[lxml-dev] Status of lxml 1.1.2
Greetings! I have an application that would be greatly simplified by using the stylesheet-PI support in lxml 1.1.2 Has anyone made a Windows build of 1.1.2 yet? If so, where can I get it? Also, what was finally decided on as the API for xslt processing using a stylesheet-PI? I went back and re-read the mailing list traffic on the topic, but it wasn't clear to me how the final form of the API ended up. Best Regards, Lee E. Brown (leebrown@leebrown.org)
I can build a lxml 1.1.2 on Windows. Can I get access to upload that to cheeseshop? -- Sidnei da Silva Enfold Systems http://enfoldsystems.com Fax +1 832 201 8856 Office +1 713 942 2377 Ext 214
Sidnei da Silva wrote:
I can build a lxml 1.1.2 on Windows. Can I get access to upload that to cheeseshop?
Sure, I would certainly appreciate that, and I'd be happy to give you maintainer rights so you can upload. What's your username on cheeseshop? Regards, Martijn P.S. to Stefan: I've known Sidnei for years and I trust him. :) Plus he's interested in creating windows versions of lxml which is excellent!
On 2/3/07, Martijn Faassen <faassen@startifact.com> wrote:
Sidnei da Silva wrote:
I can build a lxml 1.1.2 on Windows. Can I get access to upload that to cheeseshop?
Sure, I would certainly appreciate that, and I'd be happy to give you maintainer rights so you can upload. What's your username on cheeseshop?
sidnei
P.S. to Stefan: I've known Sidnei for years and I trust him. :) Plus he's interested in creating windows versions of lxml which is excellent!
I'm also running the lxml tests on the Windows pybots slave. :) http://www.python.org/dev/buildbot/community/all/?show=x86%20Windows%202003%20trunk&show=x86%20Windows%202003%202.5 -- Sidnei da Silva Enfold Systems http://enfoldsystems.com Fax +1 832 201 8856 Office +1 713 942 2377 Ext 214
Sidnei da Silva wrote:
On 2/3/07, Martijn Faassen <faassen@startifact.com> wrote:
I can build a lxml 1.1.2 on Windows. Can I get access to upload that to cheeseshop? Sure, I would certainly appreciate that, and I'd be happy to give you
Sidnei da Silva wrote: maintainer rights so you can upload. What's your username on cheeseshop?
sidnei
Hey, I've added you as maintainer so you should be able to upload windows versions now. Thanks! Regards, Martijn
Hi Martijn, Martijn Faassen wrote:
P.S. to Stefan: I've known Sidnei for years and I trust him. :) Plus he's interested in creating windows versions of lxml which is excellent!
Sure, I appreciate his contributions. Plus, it's even easier for us if others can upload their builds directly. (note that the tar balls are still signed by myself, so people who care about trusted sources - and who care to trust me - can always build their lxml from the release sources) Regards, Stefan
On 2/6/07, Stefan Behnel <stefan_ml@behnel.de> wrote:
Sure, I appreciate his contributions. Plus, it's even easier for us if others can upload their builds directly. (note that the tar balls are still signed by myself, so people who care about trusted sources - and who care to trust me - can always build their lxml from the release sources)
Thank you! I've just uploaded 1.1.2 installer for Python 2.4. Is there interest in getting a 2.5 binary too? I believe there's lots of people on 2.5, as the PyWin32 installers for 2.5 downloads are pretty close to the 2.4 downloads. BTW, how do you sign your tarballs? Signing the Windows installer is possible (Authenticode) but requires a SSL Certificate. -- Sidnei da Silva Enfold Systems http://enfoldsystems.com Fax +1 832 201 8856 Office +1 713 942 2377 Ext 214
Alright. So I've looked at 1.1.1 and saw that it had both eggs and installers for 2.4 and 2.5, so I've did the same for 1.1.2. :) -- Sidnei da Silva Enfold Systems http://enfoldsystems.com Fax +1 832 201 8856 Office +1 713 942 2377 Ext 214
Hi Sidnei, Sidnei da Silva wrote:
BTW, how do you sign your tarballs? Signing the Windows installer is possible (Authenticode) but requires a SSL Certificate.
setup.py sdist bdist_egg upload --sign [--identity ...] That signs the (source-)packages that were built in the same run and uploads them to cheeseshop, including their signatures. Stefan
Greetings! I've been playing with the windows/python2.4 build of lxml 1.1.2 that Sidnei just put up. I presume from the previous mailing list traffic and some code introspection that this is the "right" way to handle xml-stylesheet PIs: xml_tree = etree.parse(xml_data) xsl_pi = xml_tree.getroot().getprevious() xsl_tree = xsl_pi.parseXSL() transformer = etree.XSLT(xsl_tree) result = transformer(xml_tree) There's one suprise, though: I had thought from the mailing list discussion that 'href' attribute would be accessible by the get() and set() methods - but it isn't; everything past the tag is kept simply as text. (I presume that it inherited this behavior from some processing instruction base class.) Would it be possible to add get() and set() methods in a future release?
Hi, Lee Brown wrote:
I presume from the previous mailing list traffic and some code introspection that this is the "right" way to handle xml-stylesheet PIs:
xml_tree = etree.parse(xml_data) xsl_pi = xml_tree.getroot().getprevious() xsl_tree = xsl_pi.parseXSL() transformer = etree.XSLT(xsl_tree) result = transformer(xml_tree)
There's one suprise, though: I had thought from the mailing list discussion that 'href' attribute would be accessible by the get() and set() methods - but it isn't; everything past the tag is kept simply as text.
... which is basically how PIs look like according to the XML spec. I just added a fake implementation for get() that parses the text for attribute-like text sequences. For simplicity, however, the set() method only supports setting the href 'attribute' for now. Have fun, Stefan
participants (5)
-
Lee Brown -
Lee Brown -
Martijn Faassen -
Sidnei da Silva -
Stefan Behnel