lxml - The Python XML Toolkit November 2015

lxml@python.org

14 participants
16 discussions

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

Building lxml statically for MeVisLab
by Corvus Corax 21 Jan '16

21 Jan '16

Hi, I'm trying to build lxml for MeVisLab 2.7 on Windows 7 x64. Therefore I'm using the Python 2.7 delivered with MeVisLab and MS Visual Studio 2013 Professional. As my workplace is behind a proxy I had to configure the setup.py and buildlibxml.py to use the already downloaded libraries. How I did this is described in the appended build-changes.txt. So when trying to build lxml it fails with the output in build.log. It looks like it's trying to rebuild lxml.etree, but does it even have to? Would you please help me with this? I don't know what to do from here on. Sincerely, Corbie

3 5

Relax NG Compact syntax support
by Dirkjan Ochtman 27 Dec '15

27 Dec '15

Hi all, I recently had a situation at work where I wanted to use the RELAX NG Compact syntax to write a schema for some XML configuration files we are using. Having happily worked with lxml before, I googled around to see if I could feed it RNC schemas somehow, and was disappointed to only find some mailing list threads about this not being possible. There was some Python code by David Mertz that implemented a small subset of RNC, but this was deemed to limited to be fit for integration with lxml. I've since spent quite some time looking at rnc2rng and polishing it. My fork is here: https://github.com/djc/rnc2rng It now supports almost all of the syntax surface according to the RNC spec, I've created a fairly comprehensive regression test set (with about 90% coverage right now), and it works successfully on some relatively large real-world schemas that I ran into. Would you be interested to collaborate on somehow providing support for rnc2rng in lxml? Cheers, Dirkjan

2 11

lxml support of group condition for xpath ?
by Thibault Clerice 27 Nov '15

27 Nov '15

Hi there, I am truly sorry if the question was asked before, I have searched but it either seems it was not asked, or I do not use the right words... I am trying to deal with group node condition in xpath, /ie/ xpath like //div/(descendant::p|descendant::l)[@n='1'] //div/(ns:p|ns:l)[@n='1'] While this seems to be supported in xpath, I cannot find a way to make it work. My hands are a little tied here because I have not that much freedom about the xpath in itself, I need to be able to support a xpath like that, or rather, I can't go with another simpler route like //div/p[@n='1'] or //div/l[@n='1'] //ns:div/ns:p[@n='1'] or //ns:div/ns:l[@n='1'] The weird thing is that the following xpath would work (//tei:l|//tei:p)[@n='1'] But the moment I add something front of it, it breaks. [node for node in xml.xpath("(//tei:l|//tei:p)[@n='1']", namespaces={"tei": " http://www.tei-c.org/ns/1.0"})] Thank you for your time and help Best Thibault

4 6

Fwd: [xml] Release of libxml2-2.9.3
by Stefan Behnel 25 Nov '15

25 Nov '15

-------- Weitergeleitete Nachricht -------- Betreff: [xml] Release of libvirt-2.9.3 Datum: Fri, 20 Nov 2015 18:17:56 +0800 Von: Daniel Veillard <veillard(a)redhat.com> An: xml(a)gnome.org This is a security release, I didn't tried to push a number of other patches considering urgency. That release is dedicated to the memory of Bill Brack who was my co-maintainer for many years on libxml2 and libxslt, we became friends, he has a huge influence still on way I do things. Unfortunately he passed away last February. I'm sure he would have commented that celebrating his legacy with a release with so many CVE would be a tribute to his programming skills, because he always approached life with a sense of humor. RIP Bill, the code still lives but OpenSource is more about people than code ! So yes that release is packed with Security and ugly bugs fixes, more than overall improvements, I have put signed tarballs and rpms to the usual place at ftp://xmlsoft.org/libxml2/ Update is strongly suggested ! Security: - CVE-2015-8242 Buffer overead with HTML parser in push mode (Hugh Davenport) - CVE-2015-7500 Fix memory access error due to incorrect entities boundaries (Daniel Veillard) - CVE-2015-7499-2 Detect incoherency on GROW (Daniel Veillard) - CVE-2015-7499-1 Add xmlHaltParser() to stop the parser (Daniel Veillard) - CVE-2015-5312 Another entity expansion issue (David Drysdale) - CVE-2015-7497 Avoid an heap buffer overflow in xmlDictComputeFastQKey (David Drysdale) - CVE-2015-7498 Avoid processing entities after encoding conversion failures (Daniel Veillard) - CVE-2015-8035 Fix XZ compression support loop (Daniel Veillard) - CVE-2015-7942-2 Fix an error in previous Conditional section patch (Daniel Veillard) - CVE-2015-7942 Another variation of overflow in Conditional sections (Daniel Veillard) - CVE-2015-1819 Enforce the reader to run in constant memory (Daniel Veillard) - CVE-2015-7941_2 Cleanup conditional section error handling (Daniel Veillard) - CVE-2015-7941_1 Stop parsing on entities boundaries errors (Daniel Veillard) Documentation: - Correct spelling of "calling" (Alex Henrie) - Fix a small error in xmllint --format description (Fabien Degomme) - Avoid XSS on the search of xmlsoft.org (Daniel Veillard) Portability: - threads: use forward declarations only for glibc (Michael Heimpold) - Update Win32 configure.js to search for configure.ac (Daniel Veillard) - os400: lot of docs fixes and mprovements (Patrick Monnerat) Bug Fixes: - Bug on creating new stream from entity (Daniel Veillard) - Fix some loop issues embedding NEXT (Daniel Veillard) - Do not print error context when there is none (Daniel Veillard) - Avoid extra processing of MarkupDecl when EOF (Hugh Davenport) - Fix parsing short unclosed comment uninitialized access (Daniel Veillard) - Add missing Null check in xmlParseExternalEntityPrivate (Gaurav Gupta) - Fix a bug in CData error handling in the push parser (Daniel Veillard) - Fix a bug on name parsing at the end of current input buffer (Daniel Veillard) - Fix the spurious ID already defined error (Daniel Veillard) - Fix previous change to node sort order (Nick Wellnhofer) - Fix a self assignment issue raised by clang (Scott Graham) - Fail parsing early on if encoding conversion failed (Daniel Veillard) - Do not process encoding values if the declaration if broken (Daniel Veillard) - Silence clang's -Wunknown-attribute (Michael Catanzaro) - xmlMemUsed is not thread-safe (Martin von Gagern) - Fix support for except in nameclasses (Daniel Veillard) - Fix order of root nodes (Nick Wellnhofer) - Allow attributes on descendant-or-self axis (Nick Wellnhofer) - Fix the fix to Windows locking (Steve Nairn) - Fix timsort invariant loop re: Envisage article (Christopher Swenson) - Don't add IDs in xmlSetTreeDoc (Nick Wellnhofer) - Account for ID attributes in xmlSetTreeDoc (Nick Wellnhofer) - Remove various unused value assignments (Philip Withnall) - Fix missing entities after CVE-2014-3660 fix (Daniel Veillard) - Revert "Missing initialization for the catalog module" (Daniel Veillard) Improvements: - Reuse xmlHaltParser() where it makes sense (Daniel Veillard) - Add xmlHaltParser() to stop the parser (Daniel Veillard) - xmlStopParser reset errNo (Daniel Veillard) - Reenable xz support by default (Daniel Veillard) - Recover unescaped less-than character in HTML recovery parsing (Daniel Veillard) - Allow HTML serializer to output HTML5 DOCTYPE (Shaun McCance) - Regression test for bug #695699 (Nick Wellnhofer) - Add a couple of XPath tests (Nick Wellnhofer) - Add Python 3 rpm subpackage (Tomas Radej) - libxml2-config.cmake.in: update include directories (Samuel Martin) - Adding example from bugs 738805 to regression tests (Daniel Veillard) Thanks everybody for contributions to this release, I know there is a lot of other non-security oriented patches floating around, now that is mostly off my back, I will start looking at those. Reminders on the list may be helpful ! Daniel -- Daniel Veillard | Open Source and Standards, Red Hat veillard(a)redhat.com | libxml Gnome XML XSLT toolkit http://xmlsoft.org/ http://veillard.com/ | virtualization library http://libvirt.org/ _______________________________________________ xml mailing list, project page http://xmlsoft.org/ xml(a)gnome.org https://mail.gnome.org/mailman/listinfo/xml

1 0

Is there a way to stop the HTMLParser rewriting invalid HTML tags?
by Austin Platt 25 Nov '15

25 Nov '15

Hello, I have a question regarding the HTMLParser in lxml. Is there a way to make it less 'strict'? For example, as I have it currently configured, it will re-write <h1><p>Hello</p></h1> to <h1></h1><p>Hello</p> The HTML spec does not allow <p> tags to be contained within <h1> tags. However, for my specific use case, I would like to try and leave the html as close to the original html as possible even if it is invalid. The code I am using presently is as follows: >>> h = "<h1><p>Hello</p></h1>" >>> etree_parser = etree.HTMLParser() >>> tree = etree.fromstring(h, parser=etree_parser) >>> etree.tostring(tree, method='html') The version of lxml I am using is 3.5. So I was wondering if there was a way to disable this re-ordering of the tags so that the <p> would remain as a child of the <h1>? Thanks!

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 November 2015