Mailman 3 February 2017 - lxml - The Python XML Toolkit

[lxml-dev] lxml has its page on launchpad
by Stefan Behnel 11 Apr '23

11 Apr '23

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

9 9

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

10 Apr '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/>

6 6

[lxml-dev] Reparenting a node
by Lawrence Oluyede 30 Jan '23

30 Jan '23

I have a doc A and a doc B, I'd like to put a node extracted from A in the document B but I always get a ValueError: ValueError: Element is not a child of this node. I didn't find any "setparent" in the API. How can I do this? -- Lawrence, oluyede.org - neropercaso.it "It is difficult to get a man to understand something when his salary depends on not understanding it" - Upton Sinclair

3 2

[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] 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

Re: [lxml] Building latest version of lxml for Python 2.7 on Windows 32, support libraries
by Benoit Bernard 22 Feb '17

22 Feb '17

In-Reply-To=< CACiMDdfjTECwYcHmvw2bjCTB_SFZaGMw4DXkUQb2npJ1Hvc+Qw(a)mail.gmail.com> I've already done something similar, but with x64 packages. To build a wheel file for lxml, and link to static dependencies that you've already downloaded or compiled yourself, you need to do this: 1) Modify the STATIC_INCLUDE_DIRS and STATIC_LIBRARY_DIRS variables in setup.py to point to your already downloaded/compiled dependencies. 2) Use the following command to build a wheel file for lxml: python setup.py bdist_wheel --static This should compile lxml and build a wheel file that links against the static dependencies. If you want more details, check out my blog post here: https://benbernardblog.com/how-to-build-lxml-and-get-its-debug-symbols-on-w… Hope this helps! Benoit

2 1

memory allocation failure
by Martin Mueller 20 Feb '17

20 Feb '17

I recently upgraded to Python 3.6. and lxml 3.7. In running a script on 500 files I get the following error message approximately after running about 60 files: Traceback (most recent call last): File "/Users/martin/Dropbox/PycharmProjects/earlyprint/process_eebo_sample/simple_eebochange.py", line 88, in <module> tree= etree.parse(filename, parser) File "src/lxml/lxml.etree.pyx", line 3427, in lxml.etree.parse (src/lxml/lxml.etree.c:81110) File "src/lxml/parser.pxi", line 1811, in lxml.etree._parseDocument (src/lxml/lxml.etree.c:117841) File "src/lxml/parser.pxi", line 1837, in lxml.etree._parseDocumentFromURL (src/lxml/lxml.etree.c:118188) File "src/lxml/parser.pxi", line 1741, in lxml.etree._parseDocFromFile (src/lxml/lxml.etree.c:117100) File "src/lxml/parser.pxi", line 1138, in lxml.etree._BaseParser._parseDocFromFile (src/lxml/lxml.etree.c:111646) File "src/lxml/parser.pxi", line 595, in lxml.etree._ParserContext._handleParseResultDoc (src/lxml/lxml.etree.c:105102) File "src/lxml/parser.pxi", line 706, in lxml.etree._handleParseResult (src/lxml/lxml.etree.c:106810) File "src/lxml/parser.pxi", line 635, in lxml.etree._raiseParseError (src/lxml/lxml.etree.c:105664) File "/users/martin/dropbox/shcdemo-shctexts-d780443e41f0/162-A04656.xml", line 317 lxml.etree.XMLSyntaxError: Memory allocation failed, line 317, column 18 I have a machine with 32 gig of memory and watching memory use on both Python ad Pycharm the memory usage figures (100 MB, 700 MB) are not out of ordinary for what I’m doing. The failure has nothing to with whatever is in the file because it will work fine if I start the run at the previous file. The failure is very sudden, unlike in other situations where a run through thousands of files slowed down to a crawl because the system kept all ids in memory and finally stopped. Pycharm has 4 gigabytes allocated to it and on the face of it the scope of this current script is well below other scripts that ran through thousands of files without problem. I’ll be grateful for any tips on what to look for and where. BTW, adding the filename of the current file to the error report is a real blessing!

1 0

Somne newby questions on lxml
by Peter Van Epp 19 Feb '17

19 Feb '17

I'd search the archives for answers to these questions (and to know it the broken links are already reported) but the links to the archive site appear to be broken (and a google search didn't do much better) on both the http://lxml.de/3.4/ and https://mailman-mail5.webfaction.com/listinfo/lxml web pages. That said, I'm new to both python and lxml and mostly new to xml/svg too. I've been fighting with the perl bindings to the libxml2 C library without much success, so I decided to see what python had to offer. I'm trying to make changes to the svg file output from Inkscape so I need to read the svg, make changes (which I have figured out how to do in perl) and then write the file back out. That all works in perl except pretty printing is broken. In python, I can somewhat make pretty printing work, but am struggling with the output file. Using this (partial here, fed the complete file to the script) svg file as input: <?xml version="1.0" encoding="UTF-8" standalone="no"?> <svg xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:cc="http://creativecommons.org/ns#" xmlns:rdf="http://www.w3.org/1999/02/22-rdf-syntax-ns#" xmlns:svg="http://www.w3.org/2000/svg" xmlns="http://www.w3.org/2000/svg" id="svg" enable-background="new 0 0 22.484 43.997" xml:space="preserve" height="0.80000007in" viewBox="0 0 71.999791 57.600007" width="1in" version="1.1" docname="Ammeter_4wire_led_1_schematic.svg" y="0" x="0" gorn="0"><metadata id="metadata3411"><rdf:RDF><cc:Work rdf:about=""><dc:format>image/svg+xml</dc:format><dc:type rdf:resource="http://purl.org/dc/dcmitype/StillImage" /><dc:title></dc:title></cc:Work></rdf:RDF> ... in to this python script (under cygwin on Windows). I removed the user land pretty printing function that will actually pretty print the bulk of the svg code after the name space stuff: #!/usr/bin/python # A python xml pretty_print script (which works on svg files unlike the # builtin version!). # Import os and sys to get file rename and the argv stuff import os,sys # and the lxml library for the xml from lxml import etree # Start of the main script if len(sys.argv) < 2: # No input file so print a usage message and exit. s = str(sys.argv[0]) + ': Usage: ' + str(sys.argv[0]) + ' xml_file' print s sys.exit() # Parse the xml document try: file = sys.argv[1] parser = etree.XMLParser(remove_blank_text=True) doc = etree.parse(file) except IOError: print 'Error: can\'t find or read file ' + file sys.exit() else: doc.write(sys.stdout, pretty_print=True) # doc.write(sys.stdout, xml_declaration=True, encoding="UTF-8", standalone=False, pretty_print=True) sys.exit() produces this output: <svg xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:cc="http://creativecommons.org/ns#" xmlns:rdf="http://www.w3.org/1999/02/22-rdf-syntax-ns#" xmlns:svg="http://www.w3.org/2000/svg" xmlns="http://www.w3.org/2000/svg" id="svg" enable-background="new 0 0 22.484 43.997" xml:space="preserve" height="0.80000007in" viewBox="0 0 71.999791 57.600007" width="1in" version="1.1" docname="Ammeter_4wire_led_1_schematic.svg" y="0" x="0" gorn="0"> <metadata id="metadata3411"> <rdf:RDF> <cc:Work rdf:about=""> <dc:format>image/svg+xml</dc:format> <dc:type rdf:resource="http://purl.org/dc/dcmitype/StillImage"/> <dc:title/> </cc:Work> </rdf:RDF> There are two things wrong here: first the <?xml version="1.0" encoding="UTF-8" standalone="no"?> line is missing in the output. I have figured out that it can be added via the commented out output statement in the python code as long as I know (or assume I know) what the encoding was, but I would prefer to copy the values from the input line through (which is what the perl bindings do). Is there a way to do that that I'm not finding? Then the pretty printing has failed on the name space xml at the top of the file (possibly because I haven't done something necessary to register the name spaces?) I'm first looking to be able to read in and write out (without making any changes) the svg file so I know at least that works before I start changing things but am not having much luck at it. There are almost no examples that google can find of code that does this (I found the output paramters in the svgutils package on github which uses lxml, but he too is assuming he knows what the encoding is, and doesn't copy the input settings). Can anyone suggest a solution or point me at documentation or preferably examples of how it is done (or at a more suitable mailing list if this isn't it)? Peter Van Epp

2 1

Building latest version of lxml for Python 2.7 on Windows 32, support libraries
by Tom Kacvinsky 17 Feb '17

17 Feb '17

I would like to build the latest version of lxml for Python 2.7 for Windows 32, using the latest versions of zlib, iconv, libxslt and libxml2 as the wheel files that use the later versions of the support libraries are only for Python 3.x However, the notes for building on Windows say to use setup.py bdist_wininst, which hides the guts of choosing which support libraries to use (I'd like to specifiy ones I've built, not ones automatically downloaded from the internet). Also, how cython plays into this is also lost. Any tips? I am not afraid to dig in, I just need a starting point. Also of note, I would search the archives for this information, but gmane is not allowing me access to the search feature for the lxml archives. Thanks and regards, Tom

2 1

etree.cpython-34m.so: undefined symbol: PyExc_SystemError
by Финковский Игорь 17 Feb '17

17 Feb '17

2 1