Mailman 3 May 2018 - 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

Re: [lxml] Personal problems with resolve_string
by Duthie, Roger J.A. May 23, 2018

May 23, 2018

P.S. The functions were only a quick test for myself, so the names are not PEP8. However, I've ended up sharing them, so you're right and PEP8 code is a good habit to form. Have you heard Raymond Hettinger talking about PEP8? It's quite amusing and he's a good public speaker: https://www.youtube.com/watch?v=wf-BqAjZb8M [https://www.bing.com/th?id=OVP.-HpEWP8D7U77A7vY37GFKwEsCs&pid=Api]<https://www.youtube.com/watch?v=wf-BqAjZb8M> Raymond Hettinger - Beyond PEP 8 -- Best practices for beautiful intelligible code - PyCon 2015<https://www.youtube.com/watch?v=wf-BqAjZb8M> www.youtube.com "Speaker: Raymond Hettinger Distillation of knowledge gained from a decade of Python consulting, Python training, code reviews, and serving as a core developer. Learn ... ________________________________ From: Jens Quade <jq(a)qdevelop.de> Sent: 22 May 2018 23:59:56 To: Duthie, Roger J.A. Subject: Re: [lxml] Personal problems with resolve_string Hi, I haven’t worked with the Resolver class, but if you call the method via the class (and not by self.), shouldn’t the first parameter be self? > class simple_string_resolver(etree.Resolver): > > def resolve(self, url, id, context): ... > # pass this byte object to the resolve_string method > return etree.Resolver.resolve_string(content, id, context, base_url=url) according to http://lxml.de/1.3/resolvers.html#resolvers self.resolve_string( or etree.Resolver.resolve_string(self, should work. (and do the same, as long as you do not overwrite resolve_string in your simple_string_resolver class.). Also, you may want to follow PEP 8 https://www.python.org/dev/peps/pep-0008/ when naming things (like SimpleStringResolver). best, jens ________________________________ This message (and any attachments) is for the recipient only. NERC is subject to the Freedom of Information Act 2000 and the contents of this email and any reply you make may be disclosed by NERC unless it is exempt from release under the Act. Any material supplied to NERC may be stored in an electronic records management system. ________________________________

2 2

Re: [lxml] Personal problems with resolve_string
by Duthie, Roger J.A. May 23, 2018

May 23, 2018

Thanks, Jens, that's the answer. As I say, I'll probably have more questions about the resolvers in time. Rg. ________________________________ From: Jens Quade <jq(a)qdevelop.de> Sent: 22 May 2018 23:59:56 To: Duthie, Roger J.A. Subject: Re: [lxml] Personal problems with resolve_string Hi, I haven’t worked with the Resolver class, but if you call the method via the class (and not by self.), shouldn’t the first parameter be self? > class simple_string_resolver(etree.Resolver): > > def resolve(self, url, id, context): ... > # pass this byte object to the resolve_string method > return etree.Resolver.resolve_string(content, id, context, base_url=url) according to http://lxml.de/1.3/resolvers.html#resolvers self.resolve_string( or etree.Resolver.resolve_string(self, should work. (and do the same, as long as you do not overwrite resolve_string in your simple_string_resolver class.). Also, you may want to follow PEP 8 https://www.python.org/dev/peps/pep-0008/ when naming things (like SimpleStringResolver). best, jens ________________________________ This message (and any attachments) is for the recipient only. NERC is subject to the Freedom of Information Act 2000 and the contents of this email and any reply you make may be disclosed by NERC unless it is exempt from release under the Act. Any material supplied to NERC may be stored in an electronic records management system. ________________________________

1 0

Personal problems with resolve_string
by Duthie, Roger J.A. May 22, 2018

May 22, 2018

Hi LXML mailing list, I'm working on a metadata validator and we're using LXML to do the XML wrestling. I have a few questions about the URI resolvers brewing, but I'm gathering some clear evidence for the questions I would like to ask about that. In the meantime, while I have been gathering said evidence, I've come across something strange related to the lxml.etree.Resolver.resolve_string method. I wonder if it's a bug, and it whether it's related to Python 2 vs Python 3. If I have an arbitrary, but valid, XML file at a local path 'file:///something-or-other/test.xml' I can attempt to pass this through the resolver system by performing the following: from lxml import etree from urllib3.util.url import parse_url class simple_string_resolver(etree.Resolver): def resolve(self, url, id, context): # get the correct part of the URL url_components = parse_url(url) # get contents of the XML file with open(url_components.path, mode='rb') as f: contents = f.read() # pass this byte object to the resolve_string method return etree.Resolver.resolve_string(content, id, context, base_url=url) Traceback (most recent call last): File "/home/XXXXX/.p2/pool/plugins/org.python.pydev.core_6.3.3.201805051638/pysrc/_pydevd_bundle/pydevd_exec2.py", line 3, in Exec exec(exp, global_vars, local_vars) File "<console>", line 1, in <module> File "src/lxml/docloader.pxi", line 61, in lxml.etree.Resolver.resolve_string (src/lxml/lxml.etree.c:97816) TypeError: argument must be a byte string or unicode string I get the same error with the alteration of the file open parameters: with open(url_components.path, mode='rt', encoding='utf_8') as f: contents = f.read() I've checked that the contents variable is what I expect it to be and tried to encode() and decode() against the contents string, but no avail! I've even tried: etree.Resolver.resolve_string(b'<xml></xml>', id, context, base_url=url) ...and... etree.Resolver.resolve_string(u'<xml></xml>', id, context, base_url=url) ...with the same result. Any ideas? Surely, either or both of the byte string or the UTF-8 encoded Python 3 string should work!? Am I missing something obvious? I'm using Python 3.4 and LXML 3.8.0. All the best, Roger ________________________________ This message (and any attachments) is for the recipient only. NERC is subject to the Freedom of Information Act 2000 and the contents of this email and any reply you make may be disclosed by NERC unless it is exempt from release under the Act. Any material supplied to NERC may be stored in an electronic records management system. ________________________________

1 0

lxml: linkage with zlib
by Nehal J Wani May 14, 2018

May 14, 2018

Hello Everyone, If the lxml C extension links to libxml2 and libxslt; and zlib is used by libxml2 directly, then why does the extension itself need to link to libz ? I was trying to compile the lxml on a CentOS 6 machine with my own builds of libxslt and libxml2, with libxml2 already having zlib.so in it's DT_NEEDED section. When I build lxml, the C extension generated also ended up having zlib.so in it's DT_NEEDED section. The lines related to this seem to be: https://github.com/lxml/lxml/blob/master/setupinfo.py#L271-L272 What's the reason behind doing this? Cheers! Nehal J Wani

2 1

What is the correct way to tostring() except that the outer most tag should be removed?
by Peng Yu May 14, 2018

May 14, 2018

Hi, I'd like to get the text that would be got from tostring() except removing the outmost tag. Something like <foo>abcxyz123<h>f</h>uvw</foo> should be returned as abcxyz123<h>f</h>uvw I could do so by calling tostring() then use regex to remove the outermost tag. Alternatively, the code below can be customized. But I feel the 2nd approach is an overkill for this problem. Does anybody know what is the best approach for this problem? Thanks. https://stackoverflow.com/questions/11677411/python-lxml-access-text?answer… -- Regards, Peng

4 11