> -----Ursprüngliche Nachricht----- > Von: [email protected] > [mailto:[EMAIL PROTECTED] Im Auftrag von Philip Jenvey > Gesendet: Donnerstag, 24. Januar 2008 22:31 > An: [email protected] > Betreff: Re: Routes and WebHelpers status, and lxml > > > > On Jan 22, 2008, at 3:46 PM, Mike Orr wrote: > > > > > I'm working on a basic Routes implementation according to > the spec on > > the wiki. Ben is helping with the unit tests and some of > the coding. > > I hope to get a partial-feature release by early February. > > > > I'm still undecided about WebHelpers' HTML building: ElementTree, > > lxml, or something else. I think we'll just try both of > those and see > > which works better. > > > > Advantages of ElementTree: > > - No installation hassles. > > > > Advantages of lxml: > > - It's becoming common in other Python projects, > potentially emerging > > as a standard.
Just my 2cents: I just decided after some research to use lxml in all of my projects, and I guess my decission tree is comparable to that many other Python developers out there. I would bet lxml is the emerging standard. But AFAIK does lxml mimick the ElementTree API. Maybe a "workaround" for the time beeing would be that Pylons itself uses only API features common in both packages, and let the users/developers decide what package (and additional features) they want. > > Installing lxml: > > - Debian/Ubuntu require the libxml2-dev and libxslt-dev packages. > > - Precompiled Windows eggs are on PyPI for the non-latest > development > > versions. These may require downloading and installing manually to > > prevent easy_install from trying to compile from source. I just installed lxml on my Windows machine (without any C compiler support) yesterday. First try with easy_install lxml resolved to lxml-2.0.1beta (or something like that) Installation failed with some error messages. Second try with lxml=1.3.6 was successful. Without any compilation, the packages is already pre-built with C-libs included. The HTML and CSS features added with 2.0 sound very interesting and promising, also the speed and easy-to-use handling of XML. So maybe the best approach would be: - allow ElementTree or lxml - use the common API set inside Pylons - switch fully to lxml at a later stage (Pylons 1.5, Pylons 2) as soon as lxml provides precompiled C-libs both for Windows and Linux for the various distros. Just my 2cents, Andrew --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "pylons-devel" group. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/pylons-devel?hl=en -~----------~----~----~----~------~----~------~--~---
