Re: [Zope-dev] lxml and z3c.form strategy?
2008/9/16 Roger Ineichen [EMAIL PROTECTED]: What is the reason why z3c.* packages should use z3c.pt and fallback to a new concept rather then stay with PageTemplate if no lxml is installed and z3c.pt is useless? There seems to be some confusion here, and I understand why this has arisen, but let me repeat what Chris also has mentioned: There's absolutely no trace of XML left after a template is compiled (not so for Genshi templates, but that's a different story). The *only* reason I opted for lxml is that it seemed to provide the best parsing functionality. However, ``xml.etree`` aka ElementTree seems to be a good candidate, too. Is the fallback to xml.etree faster and then the old stable PageTemplate implementation? See above. \malthe ___ Zope-Dev maillist - Zope-Dev@zope.org http://mail.zope.org/mailman/listinfo/zope-dev ** No cross posts or HTML encoding! ** (Related lists - http://mail.zope.org/mailman/listinfo/zope-announce http://mail.zope.org/mailman/listinfo/zope )
Re: [Zope-dev] lxml and z3c.form strategy?
On Tue, Sep 16, 2008 at 03:29:13PM +0200, Malthe Borch wrote: 2008/9/16 Roger Ineichen [EMAIL PROTECTED]: That's fine for me. But the question is what happens on a production server. Does the missing lxml end in useing a slow fallback implementation or does it use the old style PageTempalte? Without lxml, it'll use ``xml.etree`` to parse the template and there a few differences, most of which have been addressed at this point. Is that ElementTree that was only included from Python 2.5? In other words, z3c.pt + python2.4 - lxml = fail? Marius Gedminas -- Q: How many IBM CPU's does it take to execute a job? A: Four; three to hold it down, and one to rip its head off. signature.asc Description: Digital signature ___ Zope-Dev maillist - Zope-Dev@zope.org http://mail.zope.org/mailman/listinfo/zope-dev ** No cross posts or HTML encoding! ** (Related lists - http://mail.zope.org/mailman/listinfo/zope-announce http://mail.zope.org/mailman/listinfo/zope )
Re: [Zope-dev] lxml and z3c.form strategy?
On Tuesday 16 September 2008, Marius Gedminas wrote: Is that ElementTree that was only included from Python 2.5? In other words, z3c.pt + python2.4 - lxml = fail? I guess we have to figure out a clever way to make a special extra requires for Python 2.4, since elementtree and cElementTree are available in PyPI. Regards, Stephan -- Stephan Richter Web Software Design, Development and Training Google me. Zope Stephan Richter ___ Zope-Dev maillist - Zope-Dev@zope.org http://mail.zope.org/mailman/listinfo/zope-dev ** No cross posts or HTML encoding! ** (Related lists - http://mail.zope.org/mailman/listinfo/zope-announce http://mail.zope.org/mailman/listinfo/zope )
Re: [Zope-dev] lxml and z3c.form strategy?
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Stephan Richter wrote: On Tuesday 16 September 2008, Marius Gedminas wrote: Is that ElementTree that was only included from Python 2.5? In other words, z3c.pt + python2.4 - lxml = fail? I guess we have to figure out a clever way to make a special extra requires for Python 2.4, since elementtree and cElementTree are available in PyPI. Something like this in setup.py?: extra_requires = [] import sys if sys.version_info[0:2] (2, 5): extra_requires.append(...) Tres. - -- === Tres Seaver +1 540-429-0999 [EMAIL PROTECTED] Palladion Software Excellence by Designhttp://palladion.com -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.6 (GNU/Linux) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org iD8DBQFIz+ky+gerLs4ltQ4RAm4pAKCTmb/ZjE3sGI8MedXfaS7Him4YZQCgxXni RjpGBYa3JXTmt0ERUx6zwdY= =2XYw -END PGP SIGNATURE- ___ Zope-Dev maillist - Zope-Dev@zope.org http://mail.zope.org/mailman/listinfo/zope-dev ** No cross posts or HTML encoding! ** (Related lists - http://mail.zope.org/mailman/listinfo/zope-announce http://mail.zope.org/mailman/listinfo/zope )
Re: [Zope-dev] lxml and z3c.form strategy?
What's the actual issue with lxml? It's not that hard to compile it (I'm the person that compiles the official releases), just a little bit under-documented. On Tue, Sep 16, 2008 at 12:29 AM, Roger Ineichen [EMAIL PROTECTED] wrote: Malthe, Stephan I decided after along night, trying to compile lxml on a windows box, that we will not use lxml and lxml based packages like z3c.form, z3c.template, z3c.macro etc at some of our windows servers. We have to find a strategy to keep this packages free of lxml and implement the z3c.pt support in this packages in a different way. I really like your lxml based z3c.pt work. It's nice and incredible fast. What do you think about that? I know it's a hugh amount of work, but I'm willing to help with the refactoring if you like. Regards Roger Ineichen _ END OF MESSAGE ___ Zope-Dev maillist - Zope-Dev@zope.org http://mail.zope.org/mailman/listinfo/zope-dev ** No cross posts or HTML encoding! ** (Related lists - http://mail.zope.org/mailman/listinfo/zope-announce http://mail.zope.org/mailman/listinfo/zope ) -- Sidnei da Silva Enfold Systems http://enfoldsystems.com Fax +1 832 201 8856 Office +1 713 942 2377 Ext 214 ___ Zope-Dev maillist - Zope-Dev@zope.org http://mail.zope.org/mailman/listinfo/zope-dev ** No cross posts or HTML encoding! ** (Related lists - http://mail.zope.org/mailman/listinfo/zope-announce http://mail.zope.org/mailman/listinfo/zope )
Re: [Zope-dev] lxml and z3c.form strategy?
Hi Sidnei Betreff: Re: [Zope-dev] lxml and z3c.form strategy? What's the actual issue with lxml? It's not that hard to compile it (I'm the person that compiles the official releases), just a little bit under-documented. We started to use lxml in different z3c.* packages. The problem right now is that we need to ensure a stable release concept for lxml on windows. Are you doing future release for lxml? btw, are you using the Visual Studio or mingw compiler? Regards Roger Ineichen ___ Zope-Dev maillist - Zope-Dev@zope.org http://mail.zope.org/mailman/listinfo/zope-dev ** No cross posts or HTML encoding! ** (Related lists - http://mail.zope.org/mailman/listinfo/zope-announce http://mail.zope.org/mailman/listinfo/zope )
