Mailman 3 January 2009 - lxml - The Python XML Toolkit

[lxml-dev] lxml has its page on launchpad
by Stefan Behnel April 11, 2023

April 11, 2023

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 April 10, 2023

April 10, 2023

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 Jan. 30, 2023

Jan. 30, 2023

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 Jan. 11, 2023

Jan. 11, 2023

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 Aug. 31, 2022

Aug. 31, 2022

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] Compilation of lxml on Windows 64-bit
by Hanni Ali July 17, 2009

July 17, 2009

Hi All, Came across this little gem of a Python module which seems able to translate some XML reports for me nicely. I was very pleased to see a Python 2.6 installer for windows, made checking it out much easier than many modules I use. So thanks for that. However although my testing seems to confirm this is the ideal module I do need to deploy to our production environment which is a 64-bit Windows environment running Python 2.6 (I code on 32-bit box for simplicity/resource reasons). Has anyone compiled and used lxml on this platform combination? If not does anyone foresee me having any issues compiling it for this platform? Thanks, Hanni

2 7

[lxml-dev] Standalone declaration
by Ovnicraft Feb. 26, 2009

Feb. 26, 2009

Hi, i am new with lxml and is great, i created an xml now i want to make standalone declaration in my structure, how i can do it? i search in docs but i didnt good results. Thx in advance -- [b]question = (to) ? be : !be; .[/b]

2 4

Re: [lxml-dev] Unable to solve a crash on Windows with LXML
by Stefan Behnel Feb. 6, 2009

Feb. 6, 2009

Hi, I'm CC-ing the list, I hope you don't mind. I think your description is abstract enough not to reveal anything about your application. Robert Liebeskind wrote: > The trace you received was from v2.2 of lxml but we continue to > experience > the same issue with v2.5. We use XPath extensively. We do not use > XSLT. I guess you meant 2.2beta1 and 2.1.5? > 1. An etree is loaded from an xml file and the data displayed for the > user. > 2. The etree is modified as the result of user edits using a GUI I assume that this happens inside one thread. > 3. The etree is the copied using copy.deepcopy() to etree2 > 4. etree2 is passed via a queue to a thread in which it is further > processed. Try copying the tree inside the target thread, (preferably) instead of copying it inside another thread and passing it over. Trees inherit state from the thread that built them. Also, using a tree inside a thread that did not build it will result in some additional adaptation overhead. > 5. etree2 is modfied as a result of processing in its own thread. > during this processing > additional trees/elems are fetched from disk and used to modify/ > augment etree2. > 6. etree2 is copied to etree3 > 7. etree3 is sent for a additional processing in its own thread. > 8. etree2 is copied to etree4 > 9. etree 4 is sent for additional processing in its own thread. Same thing for 6/7 and 8/9. Copying the tree from inside the target thread will make things more stable. Even if multiple copying is not really memory friendly, it's very fast in lxml, so as long as we are not talking about documents with several megabytes, and as long as this thing really runs on a multi processor machine, you should be fine even with a work-around that copies the tree redundantly in both threads. > at this point the initial thread is complete and tears down. > the two additional spawned threads finish quickly and tear down as well. > These processes will succeed quite often. They fail intermittently > and result in a Windows Unhandled Exception. lxml.etree uses a per-thread dictionary that holds names of tags and attributes. That's one of the reasons why it's so fast and memory friendly. In the stack trace you showed me, it seems that a tree is freed in a different thread than the one that built it, but (for whatever reason) some of it content is still linked to a dictionary of the original thread. In this case, the tree cleanup cannot detect that the name is stored in a dictionary and will free it manually. When the originating thread goes down, either before or after the thread that freed the tree, it will destroy the dictionary that stores the name, which results in a double free. Does that help for now? Stefan

2 4

[lxml-dev] Avoiding re-parsing for document loading
by Laurence Rowe Jan. 30, 2009

Jan. 30, 2009

I have an XSLT that accesses a number of other documents. These other documents are also created in lxml. Is there a way to pass them to my stylesheet without incurring an additional parse? Laurence

3 3

[lxml-dev] Serialization to file does not report error
by Frédéric Mantegazza Jan. 29, 2009

Jan. 29, 2009

I use the following code to serialize a tree to a file: tree.write(self.__fileName, pretty_print=True, xml_declaration=True) if the file pointed by self.__fileName is not writable (not owned by the current user), the call silently exits, but the file is not written. I have to use: file_ = file(self.__fileName, 'w') tree.write(file_, pretty_print=True, xml_declaration=True) file_.close() to catch en exception in this case. I'm using lxml 1.1.1; this is an old version (from debian etch), and it might have been corrected in new release... -- Frédéric

2 2