Mailman 3 December 2013 - 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

generating html with incremental writer
by Burak Arslan 25 Sep '14

25 Sep '14

Hi, Is there a way to pass method='html' to etree.xmlfile()? Or any other way to serialize incrementally to html? Best, Burak

2 9

segfault possibly python-lxml, libxml2 related
by Matt Baker 14 Jan '14

14 Jan '14

Hi all, First off, I must admit limited abilities with debugging segfaults, so apologies for that. I run a configuration management server bcfg2 which is python based heavily utilising python-lxml. The server runs debian wheezy (recently squeeze which exhibited the problem too). It appears on the face of it that it's segfaulting during a python genshi template which reads in some XML. Please see the gdb analysis attached. Any advice or pointers or next steps in how to determine the cause of the segfault would be greatly appreciated. Thanks in advance. Matt -- Matthew Baker :: Unix/Security Team Lead Infrastructure, Systems and Operations @University of Bristol Team email: it-sysops(a)bristol.ac.uk Tel: +44(0)117 3317467 Add: Uni of Bristol, Computer Centre, Tyndal Ave, Bristol. BS8 1UD

2 6

Issue with _IncrementalFileWriter._handle_error
by Burak Arslan 02 Jan '14

02 Jan '14

Hi, (I'm working on getting lxml incremental writer to write on a twisted http request object) This is from lxml trunk, _IncrementalFileWriter in serializer.pxi cdef _handle_error(self, int error_result): if error_result != xmlerror.XML_ERR_OK: if self._writer is not None: self._writer._exc_context._raise_if_stored() _raiseSerialisationError(error_result) I could be wrong but I don't think _IncrementalFileWriter should have a separate _writer attribute. Here's the relevant bit of traceback i'm getting: File "serializer.pxi", line 637, in lxml.etree.xmlfile.__exit__ (src/lxml/lxml.etree.c:110916) File "serializer.pxi", line 870, in lxml.etree._IncrementalFileWriter._close (src/lxml/lxml.etree.c:114606) File "serializer.pxi", line 874, in lxml.etree._IncrementalFileWriter._handle_error (src/lxml/lxml.etree.c:114663) Is this a typo/bug or am I missing something? Best, Burak

2 7

Problem with default NS and attributes
by Ivan Zderadicka 23 Dec '13

23 Dec '13

Hi, I have an issue with serializing ElementTree to XML when I'm using namespaces: when namespace has a prefix everything works as expected: nsmap={'myns': 'default_namespace_uri'} root=etree.Element('{default_namespace_uri}elem', {'{default_namespace_uri}attrib':'xyz'}, nsmap=nsmap ) stream=StringIO() tree=etree.ElementTree(root) tree.write(stream) print stream.getvalue() result is <myns:elem xmlns:myns="default_namespace_uri" myns:attrib="xyz"/> However if I set the namespace as a default namespace like this: nsmap={None: 'default_namespace_uri'} root=etree.Element('{default_namespace_uri}elem', {'{default_namespace_uri}attrib':'xyz'}, nsmap=nsmap ) stream=StringIO() tree=etree.ElementTree(root) tree.write(stream) print stream.getvalue() result is then strange: <elem xmlns="default_namespace_uri" xmlns:ns0="default_namespace_uri" ns0:attrib="xyz"/> as you can see namespace is defined twice - first as default and second with prefix ns0, which is then used for attribute. I would expect that xml in this case should look like this: <elem xmlns="default_namespace_uri" attrib="xyz"/> This looks to me as a bug or am I missing something ? Regards Ivan

2 2

lxml 3.3.0 beta 2 released
by Stefan Behnel 21 Dec '13

21 Dec '13

Hi all, I just released the second beta of lxml 3.3.0, containing some major bug fixes. Please give it all the testing you can afford, especially for the new iterparse() code. The documentation is here: http://lxml.de/ Download: http://lxml.de/files/lxml-3.3.0beta2.tgz Signature: http://lxml.de/files/lxml-3.3.0beta2.tgz.asc Changelog: http://lxml.de/3.3/changes-3.3.0beta2.html Github: https://github.com/lxml/lxml/commit/81d0036486d4ce81bdd86774ea95d002fdd6d0e1 This release was built using Cython 0.19.2. If you are interested in commercial support or customisations for the lxml package, please contact me directly. Have fun, Stefan 3.3.0beta2 (2013-12-20) ======================= Features added -------------- * ``iterparse()`` supports the ``recover`` option. Bugs fixed ---------- * Crash in ``iterparse()`` for HTML parsing. * Crash in target parsing with attributes. Other changes ------------- * The safety check in the read-only tree implementation (e.g. used by ``PythonElementClassLookup``) raises a more appropriate ``ReferenceError`` for illegal access after tree disposal instead of an ``AssertionError``. This should only impact test code that specifically checks the original behaviour.

1 0