Mailman 3 March 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] html5lib tree builder in lxml 2.2
by Geoffrey Sneddon March 29, 2009

March 29, 2009

Hi, Getting around to actually looking at lxml 2.2's html5lib support, I note that it has its own treebuilder: I presume there was some reason (bugs?) that html5lib's own wasn't used. Would it be possible to get a patch for html5lib that would fix these issues (this'll need to be under the MIT license)? -- Geoffrey Sneddon <http://gsnedders.com/>

2 3

Re: [lxml-dev] [Question #65510]: How to set libxml:XML_PARSE_HUGE-option in lxml?
by Stefan Behnel March 27, 2009

March 27, 2009

bol wrote: > we are working with large text corpora (bigger than 10mb). > Lxml is used for splitting this corpora-xml-files and run via sockets (old > non-xml-using) binaries for i.e. pos-tagging or tokenizing. Ok, that gives you a) the bit of structure that you need and b) safe and portable encoding support (which I assume is critical here), so that's fine with me. After all, XML is used for all sorts of things these days... > The option XML_PARSE_HUGE should be as in libxml default off. That's what I was wondering about. It's (sort of) on by default if you use libxml2 2.6.x and 2.7.[012], but it's supposed to be off by default if you use libxml2 2.7.3 and later. That's outside of the control of lxml. So you would get one behaviour on one system and a different behaviour on another system, even with the same version of lxml. However, this is meant as a security measure to prevent traps like the billion laughs attack. Therefore, I do understand that a) most people won't notice and b) having it on by default seems like the right setting. Is there any opposition to keeping the enforced parser restrictions (limited tree depth and text node length) enabled by default in newer libxml2 versions, and to provide a parser switch for disabling them? The alternative would be to disable them by default on all libxml2 versions, and to provide a switch that enables them if libxml2 supports it. But a safe default sounds a lot better. Stefan

2 2

[lxml-dev] Version in trunk (svn:63387) doesn't compile on Fedora 9.x86_64 / Fedora 10.x86_64
by Andreas March 27, 2009

March 27, 2009

Hi, the version in trunk seems broken for Fedora 9/10. $ uname -a Linux rechner1 2.6.27.19-78.2.30.fc9.x86_64 #1 SMP Tue Feb 24 19:44:45 EST 2009 x86_64 x86_64 x86_64 GNU/Linux and $ uname -a Linux rechner2 2.6.27.7-134.fc10.x86_64 #1 SMP Mon Dec 1 22:21:35 EST 2008 x86_64 x86_64 x86_64 GNU/Linux libxml2 2.7.3 Python 2.5.1 ---- snip ---- python setup.py build_ext -i Building lxml version 2.2-63198. Building with Cython 0.11. Using build configuration of libxslt 1.1.24 Building against libxml2/libxslt in the following directory: /usr/lib64 running build_ext building 'lxml.etree' extension creating build creating build/temp.linux-x86_64-2.5 creating build/temp.linux-x86_64-2.5/src creating build/temp.linux-x86_64-2.5/src/lxml gcc -pthread -fno-strict-aliasing -DNDEBUG -O2 -g -pipe -Wall -Wp,-D_FORTIFY_SOURCE=2 -fexceptions -fstack-protector --param=ssp-buffer-size=4 -m64 -mtune=generic -D_GNU_SOURCE -fPIC -fPIC -I/usr/include/libxml2 -I/usr/include/python2.5 -c src/lxml/lxml.etree.c -o build/temp.linux-x86_64-2.5/src/lxml/lxml.etree.o -w src/lxml/lxml.etree.c:3299: error: expected ‘=’, ‘,’, ‘;’, ‘asm’ or ‘__attribute__’ before ‘__pyx_v_4lxml_5etree_XSLT_DOC_DEFAULT_LOADER’ src/lxml/lxml.etree.c:3600: error: expected declaration specifiers or ‘...’ before ‘xsltLoadType’ src/lxml/lxml.etree.c:3601: error: expected declaration specifiers or ‘...’ before ‘xsltLoadType’ src/lxml/lxml.etree.c:110035: error: expected declaration specifiers or ‘...’ before ‘xsltLoadType’ src/lxml/lxml.etree.c: In function ‘__pyx_f_4lxml_5etree__xslt_store_resolver_exception’: src/lxml/lxml.etree.c:110095: error: ‘__pyx_v_c_type’ undeclared (first use in this function) src/lxml/lxml.etree.c:110095: error: (Each undeclared identifier is reported only once src/lxml/lxml.etree.c:110095: error: for each function it appears in.) src/lxml/lxml.etree.c:110095: error: ‘XSLT_LOAD_DOCUMENT’ undeclared (first use in this function) src/lxml/lxml.etree.c: At top level: src/lxml/lxml.etree.c:110242: error: expected declaration specifiers or ‘...’ before ‘xsltLoadType’ src/lxml/lxml.etree.c: In function ‘__pyx_f_4lxml_5etree__xslt_doc_loader’: src/lxml/lxml.etree.c:110257: error: ‘__pyx_v_c_type’ undeclared (first use in this function) src/lxml/lxml.etree.c:110257: error: ‘XSLT_LOAD_DOCUMENT’ undeclared (first use in this function) src/lxml/lxml.etree.c:110280: error: ‘XSLT_LOAD_STYLESHEET’ undeclared (first use in this function) src/lxml/lxml.etree.c:110385: error: too many arguments to function ‘__pyx_f_4lxml_5etree__xslt_store_resolver_exception’ src/lxml/lxml.etree.c: In function ‘__pyx_pf_4lxml_5etree_4XSLT___call__’: src/lxml/lxml.etree.c:113230: error: ‘xsltTransformContext’ has no member named ‘dict’ src/lxml/lxml.etree.c:113241: error: ‘xsltTransformContext’ has no member named ‘dict’ src/lxml/lxml.etree.c:113253: error: ‘xsltTransformContext’ has no member named ‘dict’ src/lxml/lxml.etree.c:113262: error: ‘xsltTransformContext’ has no member named ‘dict’ src/lxml/lxml.etree.c: In function ‘initetree’: src/lxml/lxml.etree.c:147853: error: ‘__pyx_v_4lxml_5etree_XSLT_DOC_DEFAULT_LOADER’ undeclared (first use in this function) src/lxml/lxml.etree.c:147853: error: ‘xsltDocDefaultLoader’ undeclared (first use in this function) error: command 'gcc' failed with exit status 1 make: *** [inplace] Error 1 ---- snip --- Regards Andreas

2 1

Re: [lxml-dev] [Question #65510]: How to set libxml:XML_PARSE_HUGE-option in lxml?
by Stefan Behnel March 27, 2009

March 27, 2009

Hi, forwarding this to the mailing list where it belongs. bol wrote: > in lixbml2 changelog: > > Daniel Veillard Sun Jan 18 15:06:05 CET > > * include/libxml/parserInternals.h SAX2.c: add a new define > XML_MAX_TEXT_LENGHT limiting the maximum size of a single text node, > the defaultis 10MB and can be removed with the HUGE parsing option Yes, this was changed in libxml2 2.7.x. > So how can I set in lxml this HUGE-option? You currently can't, and I wonder if this should really be an option and what the default should be here. > At the moment I use a from me modified version of libxml2 (with > XML_MAX_TEXT_LENGTH set to 100MB), which solves my problem. But I hope to > find a lxml-way to solve this. Could you say something about your use case? Stefan

1 0