lxml - The Python XML Toolkit February 2011

lxml@python.org

34 participants
41 discussions

[lxml-dev] Checking whether a node is a comment/element
by Geoffrey Sneddon 11 Jan '23

11 Jan '23

Hi, What's the best way to check whether a given node is a comment or an element? For the former, I'm currently using isinstance(node, etree._Comment), which is rather obviously sub-optimal. -- Geoffrey Sneddon <http://gsnedders.com/>

4 4

[lxml-dev] lxml 2.0.5 released
by Stefan Behnel 11 Jan '23

11 Jan '23

Hi all, lxml 2.0.5 is on PyPI. This is a bug-fix-only release of the stable 2.0 series. Have fun, Stefan 2.0.5 (2008-05-01) Bugs fixed * Resolving to a filename in custom resolvers didn't work. * lxml did not honour libxslt's second error state "STOPPED", which let some XSLT errors pass silently. * Memory leak in Schematron with libxml2 >= 2.6.31.

3 4

[lxml-dev] lxml has its page on launchpad
by Stefan Behnel 21 Sep '22

21 Sep '22

Hi all, I added the lxml project to launchpad, the Ubuntu Bug-Tracker. It also has a FAQ engine and a couple of other goodies. https://launchpad.net/lxml It's easy to sign up for launchpad, BTW, no 90%-footnotes-contract. Have fun, Stefan

3 2

[lxml-dev] Building LXML Trunk
by Sidnei da Silva 31 Aug '22

31 Aug '22

Hi, I've tried to build lxml from trunk today, on Win32. Got the following error: src\lxml\etree.c(880) : error C2059: syntax error : ')' src\lxml\etree.c(881) : error C2059: syntax error : ')' src\lxml\etree.c(882) : error C2059: syntax error : ')' src\lxml\etree.c(883) : error C2059: syntax error : ')' Any clue? Smells like a Pyrex issue? -- Sidnei da Silva Enfold Systems http://enfoldsystems.com Fax +1 832 201 8856 Office +1 713 942 2377 Ext 214

4 4

[lxml-dev] confusing xpath performance characteristics
by jholg＠gmx.de 24 Aug '12

24 Aug '12

Hi, I ran into some performance characteristics of lxml/libxml2 xpath that I find rather confusing: I try to find the @type attribute of a certain element in an XML Schema (which contains lots of complexType definitions with lots of elements in them; unfortunately I can't post the schema): >>> timeit.Timer(stmt="""xpath(schema)""", setup="""from lxml import etree, objectify; schema=etree.parse('NDM.xsd').getroot(); xpath = etree.XPath('//xs:element[@name="equity"]/@type', namespaces={'xs': 'http://www.w3.org/2001/XMLSchema'})""").repeat(number=10) [0.095885038375854492, 0.096823930740356445, 0.096174955368041992] So I think I'm being smart and give a little more path information - reckoning that this should *improve* performance: >>> timeit.Timer(stmt="""xpath(schema)""", setup="""from lxml import etree, objectify; schema=etree.parse('NDM.xsd').getroot(); xpath = etree.XPath('/xs:schema//xs:element[@name="equity"]/@type', namespaces={'xs': 'http://www.w3.org/2001/XMLSchema'})""").repeat(number=10) [0.1770780086517334, 0.1775970458984375, 0.17748594284057617] Hm. Performance degrades slightly. I'm adding even more of the path to where my desired elements live in the schema: >>> timeit.Timer(stmt="""xpath(schema)""", setup="""from lxml import etree, objectify; schema=etree.parse('xsd/NDM.xsd').getroot(); xpath = etree.XPath('/xs:schema/xs:complexType//xs:element[@name="equity"]/@type', namespaces={'xs': 'http://www.w3.org/2001/XMLSchema'})""").repeat(number=10) [103.79744100570679, 103.83671712875366, 103.61817717552185] What??? >>> timeit.Timer(stmt="""xpath(schema)""", setup="""from lxml import etree, objectify; schema=etree.parse('/ae/data/pydev/hjoukl/NDM/SVN_CO/TRUNK/ndm/reference/xsd/NDM.xsd').getroot(); xpath = etree.XPath('/xs:schema/xs:complexType/*/xs:element[@name="equity"]/@type', namespaces={'xs': 'http://www.w3.org/2001/XMLSchema'})""").repeat(number=10) [0.044407129287719727, 0.044126987457275391, 0.044229030609130859] >>> Ok, this version's better than my naive approach, which seems logical to me. But why would '/xs:schema/xs:complexType//xs:element[@name="equity"]/@type' perform drastically slower than '/xs:schema/xs:complexType//xs:element[@name="equity"]/@type' ? libxml2 problem? Running the same xpaths in Oxygen I don't notice performance differences (can't profile this). Holger -- GRATIS für alle GMX-Mitglieder: Die maxdome Movie-FLAT! Jetzt freischalten unter http://portal.gmx.net/de/go/maxdome01

2 5

[lxml-dev] Codespeak shutting down: migration plans?
by Luciano Ramalho 23 Jul '11

23 Jul '11

Dear colleagues, As a long-time user of lxml I was shocked to read a message today from Holger Krekel about the end of Codespeak (see full text at the end of this). First we need to thank Holger for all these years of free service. Then we need to quickly plan and execute a migration to some other repository. I am willing to help, but I am no core developer of lxml, and in fact this is my first message ever to this mailing list, so I think we need someone better known to this community to lead the migration effort. lxml as a key piece of the Python ecosystem and for the benefit of its present and future users and the wider Python community we need to make sure it continues to be available, and to make sure as many references (pypi!) as possible point to the new canonical repository. Finally, a big thank you to Martijn, Philikon, Stefan and all the others who have built this great piece of software. Cheers, -- Luciano Ramalho programador repentista || stand-up programmer Twitter: @luciano ######################################### hi codespeak.net users, (sorry if you get mail twice, i wanted to make sure ...) after 8 years of operation codespeak.net services are bound to terminate, starting END OF FEBRUARY 2011 Background: one of the original codespeak purposes was to offer subversion (then in version 0.17) for the PyPy and other projects but today this is not too interesting given the pletora of VCS hosting solutions. Also, there aren't too many admins besides me, the hosting is costing money, PyPy's repository has moved to Bitbucket and i am re-shuffling my priorities preparing for my soon to emerge father-hood. After February 2011 i probably won't be able to help much with any transition issues or questions. The host will keep on running for a while but i give no guaruantees. Some remarks regarding termination wrt to the FEB 2011 deadline: * the subversion repo will turn read-only (and will eventually be switched off). * Shell accounts will be restricted to those people who need it *and* mail me about it. Some time later they will be gone as well. * Mailing lists will be terminated as well unless i get a mail asking me to postpone termination for a specific time. You can go to your respective mailman admin page and extract a list of members. If you mail me i can also provide a list of members. * Any remaining web docs/pages will probably continue to exist for a while but i also prefer them to be moved away by end Feb 2011. Note that the codespeak svn repository contains a lot of projects. For migration you have two options: do a flat import just of your project checkout directory into a new version system. This is super-simple, obviously. If you want to preserve history for your project please mail me and i either provide you a full dump or a filtered dump only containing your project. So long and I hope you all had a good time and enjoyed the services and also have a good transition now. see you in other places, holger krekel _______________________________________________ codespeak-ann(a)codespeak.net http://codespeak.net/mailman/listinfo/codespeak-ann

4 7

[lxml-dev] DLL issue with win32 static builds of lxml
by Scott Smith 04 Apr '11

04 Apr '11

Hi I'm looking at upgrading our python installations from 2.6(.2) to 2.7 and upgrading the packages we use to the latest versions. We use python and the mod_wsgi module in Apache 2.2 for our application server and easy_install to install egg packages. I'm currently testing on a Windows 7 machine. The current egg version of lxml that we're using (before upgrading) is: lxml-2.2.4-py2.6-win32.egg In trying to upgrade things, I've found that all the later builds of lxml cause a DLL problem through apache. For example, all of these builds (from pipy) cause the problem: lxml-2.2.8-py2.6-win32.egg lxml-2.2.8-py2.7-win32.egg lxml-2.2beta1-py2.6-win32.egg lxml-2.3beta1-py2.6-win32.egg lxml-2.3beta1-py2.7-win32.egg (Note that there are no static win32 builds available for 2.2.5-2.2.7, or I can't find them) The error thrown in the Apache logs is: mod_wsgi (pid=4812): Target WSGI script 'C:/wsgi/handler.py' cannot be loaded as Python module. mod_wsgi (pid=4812): Exception occurred processing WSGI script 'C:/wsgi/handler.py'. Traceback (most recent call last): File "C:/wsgi/handler.py", line 2, in <module> from lxml import etree ImportError: DLL load failed: The specified module could not be found. The same file works in Python 2.6 if lxml 2.2.4 is installed, but fails for any other higher version of lxml (either in python 2.6 or 2.7). I've been able to trace the problem down to the builds not being able to find the msvcr90.dll file properly. I've tried modifying path variables and other changes, but can't figure out what the problem is. A couple of other things to note: - Using just "import lxml" doesn't cause the error, just "from lxml import etree" - The problem only occurs through Apache. If I write a script that references etree and call it through the command line, the problem doesn't occur. Does anyone know what I need to do? What changed after the 2.2.4 lxml builds? Thanks for any help you can give. Scott Smith

5 5

availability of lxml 2.3 windows binaries
by Piotr Dobrogost 01 Mar '11

01 Mar '11

Hi! When could we expect to be able to download lxml 2.3 windows binaries from PyPi (http://pypi.python.org/pypi/lxml/2.3#downloads)?

3 3

Re: [lxml] Adding top-level comments to an ElementTree object
by Tyler Erickson 01 Mar '11

01 Mar '11

Marc, I understand how the append(fragment) approach shown in your example can be used to successfully add an XML Comment that is a child of the root element (see example code below), but I don't see how that approach can be used to add a top-level comment. (Also, I neglected to include the result of the print statement that shows the top-level comment in my original post. This time the result of the print statement, which shows an example of a top-level comment, is included below.) - Tyler ########################################################## # Example of using the append(fragment) approach to add a (not top level) comment ########################################################## $ python Python 2.6.6 (r266:84292, Sep 15 2010, 16:22:56) [GCC 4.4.5] on linux2 Type "help", "copyright", "credits" or "license" for more information. >>> from lxml import etree >>> from lxml.builder import E >>> # construct an Element class using the E-factory ... element = ( ... E.root( ... E.a('eggs'), ... ) ... ) >>> # wrap with an ElementTree ... element_tree = etree.ElementTree(element) >>> >>> # append a comment to the root ... element_tree.getroot().append(etree.Comment('test comment')) >>> print etree.tostring(element_tree,pretty_print=True) <root> <a>eggs</a>  </root> ########################################################## # Example of a top-level comment ########################################################## >>> from StringIO import StringIO >>> tree = etree.parse(StringIO('''\ ... <?xml version="1.0"?> ...  ... <root> ... <a>eggs</a> ... </root> ... ''')) >>> print etree.tostring(tree) <root> <a>eggs</a> </root> On Mon, Feb 28, 2011 at 2:37 PM, Graff, Marc <Marc.Graff(a)verizonwireless.com > wrote: > Attached is a method I use to insert external xml into an existing tree > > Then I print out the modified tree after all mods are complete. > > > > > > > > > > *From:* lxml-bounces(a)lxml.de [mailto:lxml-bounces@lxml.de] *On Behalf Of *Tyler > Erickson > *Sent:* Monday, February 28, 2011 3:14 PM > *To:* lxml(a)lxml.de > *Subject:* [lxml] Adding top-level comments to an ElementTree object > > > > How do you add top-level comments to an ElementTree object [1]? > > > > from lxml import etree > > from lxml.builder import E > > # construct an Element class using the E-factory > > element = ( > > E.root( > > E.a('eggs'), > > ) > > ) > > # wrap with an ElementTree > > element_tree = etree.ElementTree(element) > > > > It appears that you can do this by parsing an XML document that contains a > top-level comment (shown below), but I am unsure of how to add a top-level > comment to an existing ElementTree object. > > > > from StringIO import StringIO > > tree = etree.parse(StringIO('''\ > > <?xml version="1.0"?> > >  > > <root> > > <a>eggs</a> > > </root> > > ''')) > > print etree.tostring(tree) > > > > > > - Tyler > > > > [1] http://lxml.de/tutorial.html#the-elementtree-class >

1 0

Re: [lxml] Adding top-level comments to an ElementTree object
by Graff, Marc 28 Feb '11

28 Feb '11

Attached is a method I use to insert external xml into an existing tree Then I print out the modified tree after all mods are complete. From: lxml-bounces(a)lxml.de [mailto:lxml-bounces@lxml.de] On Behalf Of Tyler Erickson Sent: Monday, February 28, 2011 3:14 PM To: lxml(a)lxml.de Subject: [lxml] Adding top-level comments to an ElementTree object How do you add top-level comments to an ElementTree object [1]? from lxml import etree from lxml.builder import E # construct an Element class using the E-factory element = ( E.root( E.a('eggs'), ) ) # wrap with an ElementTree element_tree = etree.ElementTree(element) It appears that you can do this by parsing an XML document that contains a top-level comment (shown below), but I am unsure of how to add a top-level comment to an existing ElementTree object. from StringIO import StringIO tree = etree.parse(StringIO('''\ <?xml version="1.0"?>  <root> <a>eggs</a> </root> ''')) print etree.tostring(tree) - Tyler [1] http://lxml.de/tutorial.html#the-elementtree-class

1 0

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

2005

2004

lxml - The Python XML Toolkit February 2011