lxml - The Python XML Toolkit March 2016

lxml@python.org

7 participants
10 discussions

[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

cannot load Schematron stylesheet: "<string>:0:0:ERROR:XSLT:ERR_OK: unknown error"
by Rainer Hoerbe 08 Apr '16

08 Apr '16

I am able to reproduce an erroneous behavior with python 2.7 and 3.4l + xml 3.6.0. Processing is correct when using xsltproc directly: import lxml.etree as ET sf = 'rules/schtron/rule04E.xsl' xslt = ET.fromstring(open(sf).read()) transform = ET.XSLT(xslt) # at this point transform.error_log.lasterror contains "<string>:0:0:ERROR:XSLT:ERR_OK: unknown error" The stylesheet is: https://github.com/rhoerbe/saml_schematron/blob/master/rules/schtron/rule04… and has been generated from this schematron: https://github.com/rhoerbe/saml_schematron/blob/master/rules/schtron/rule04… The code works with other (simple?) stylesheets. Are there any restrictions in lxml that prevent the processing of ISO-schematron stylesheets? Or is this a bug that should be filed? Regards, Rainer

3 12

XML Schema API?
by Markus Schöpflin 17 Mar '16

17 Mar '16

I'm using XPath queries on XML schema documents to extract certain information from a given schema document. This works well using lxml. This approach falls short when the XML schema document uses xs:include. Now I stumbled across the XML Schema API (see https://www.w3.org/Submission/xmlschema-api/). Using the XML Schema API likely would solve all issues regarding include statements. Is it possible to use the XML Schema API with lxml? TIA, Markus

2 1

Undocumented or unwanted change in keyword parameter?
by Oliver Bestwalter 17 Mar '16

17 Mar '16

Hello, I don't want to report a bug (yet), as I don't know as what this should be reported - but it's definitely a problem. My info on the system where I reproduced it: Python : sys.version_info(major=3, minor=4, micro=3, releaselevel='final', serial=0) lxml.etree : (3, 5, 0, 0) libxml used : (2, 9, 1) libxml compiled : (2, 9, 1) libxslt used : (1, 1, 28) libxslt compiled : (1, 1, 28) In lxml==3.2.1 under Python 2.7 I instantiated it succesfully like this XmlParser([...], XMLSchema_schema=None, [...]) (note the underscore) In lxml==3.5.0 under Python 3.4 this started failing with the error: Traceback (most recent call last): File "/path/to/my/script.py", line 7, in <module> XMLSchema_schema=xmlSchema) File "src/lxml/parser.pxi", line 1437, in lxml.etree.XMLParser.__init__ (src/lxml/lxml.etree.c:120522) TypeError: __init__() got an unexpected keyword argument 'XMLSchema_schema' from lxml import etree The code looks like this: from lxml import etree xmlSchema = etree.XMLSchema(file='/path/to/some/schema.xsd') parser = etree.XMLParser( remove_blank_text=True, attribute_defaults=True, XMLSchema_schema=xmlSchema) It can be fixed by just using "schema" instead of "XMLSchema_schema" as keyword argument: XmlParser([...], schema=xmlSchema, [...]) --- I had a look at the sources of both versions. The affected source line In file src/lxml/lxml.etree.pyx:1437 in both versions looks the same def __init__([...], XMLSchema schema=None, [...]): so I guess somewhere between 3.21. and 3.5.0 the type hint does not get baked into the keyword argument anymore? My question would be: Is this a bug in the documentation that fails to identify the new keyword parameter as "schema" or is this an unwanted change of the parameter that should actually remain as "XMLSchema_schema" and turned accidentally into "schema"? cheers Oliver

3 5

Next release of lxml supporting PyPy
by Pim van der Eijk (Lists) 17 Mar '16

17 Mar '16

Hi, PyPy 5.0.0 is reported to be compatible with the LXML development branch, which incorporates some improvements not yet in the 3.5.0. When is the next lxml release being planned? Most of my Python projects involve lxml, and I would like to be able to use PyPy. Kind Regards, Pim -------- Forwarded Message -------- Subject: Re: [pypy-dev] release seems ready Date: Wed, 16 Mar 2016 17:32:05 +0100 From: Pim van der Eijk (Lists) <lists(a)sonnenglanz.net> To: pypy-dev(a)python.org Did the lxml project indicate they will provide a new release soon that incorporates these fixes? I tried to build the latest development code from source, but run into many issues (lxml build server down, source package missing the pre-generated C code etc. etc.), and customer company policy wouldn't allow using a development version in production anyway. The lxml 3.5.0 does not install with pypy-5.0.0 (it used to with pypy-4.0.1, though it was too buggy to be useful), and the lxml-cffi no longer installs. On 08-03-16 15:26, Armin Rigo wrote: > Hi Matti, > > On 8 March 2016 at 15:15, matti picus <matti.picus(a)gmail.com> wrote: >> We could package it and upload as rc1, but version_info will not have rc1 >> unless we rerun the builds. Confusing. >> I prefer to apologize if we get it wrong and release a 5.0.1 bugfix > +1. Go ahead as far as I'm concerned. > > About the release notice: "As a result, lxml with its cython compiled > component passes all tests on PyPy" is not clear until the next > official lxml is released. The current lxml 3.5.0 still contains a > partially buggy workaround that tries to make it work on previous > versions of cpyext. The trunk version at https://github.com/lxml/lxml > has got this code removed, and that's the version that works. > > I'll make the ppc releases once the other releases are out. > > > A bientôt, > > Armin > _______________________________________________ > pypy-dev mailing list > pypy-dev(a)python.org > https://mail.python.org/mailman/listinfo/pypy-dev

2 2

lxml 3.6.0 released
by Stefan Behnel 17 Mar '16

17 Mar '16

Hi all, I just released lxml 3.6.0. All changes in this release came from pull requests. Thanks to everyone who contributed. The main change is support for PyPy 5.0, which is also the minimum supported version now. This should generally improve the stability and performance under PyPy. The documentation is here: http://lxml.de/ Download: http://lxml.de/files/lxml-3.6.0.tgz Signature: http://lxml.de/files/lxml-3.6.0.tgz.asc Changelog: http://lxml.de/3.6/changes-3.6.0.html Github: https://github.com/lxml/lxml/commit/79637c7c245f6439cc4b85817b12826483e3e8d5 This release was built using Cython 0.23.4. If you are interested in commercial support or customisations for the lxml package, please contact me directly. Have fun, Stefan 3.6.0 (2016-03-17) ================== Features added -------------- * GH#187: Now supports (only) version 5.x and later of PyPy. Patch by Armin Rigo. * GH#181: Direct support for `.rnc` files in `RelaxNG()` if `rnc2rng` is installed. Patch by Dirkjan Ochtman. Bugs fixed ---------- * GH#189: Static builds honour FTP proxy configurations when downloading the external libs. Patch by Youhei Sakurai. * GH#186: Soupparser failed to process entities in Python 3.x. Patch by Duncan Morris. * GH#185: Rare encoding related `TypeError` on import was fixed. Patch by Petr Demin.

1 0

lxml - pretty-print (?) - multiple consecutive key pairs per line ?
by Christoph 17 Mar '16

17 Mar '16

Hiya, excuse the highly noobistic nature of my question... I'm not a programmer, but I can write some basic python, but lxml is all new to me. In essence, I need to build an xml file to a very specific format. Unfortunately, that target format utilizes multiple keys (? semantics...) per line, without a line break, like: <key>Track ID</key><integer>971</integer> <key>Name</key><string>Citadel Station</string> <key>Artist</key><string>Disrupt</string> I found the syntax to nest multiple keys, and to white-space them properly for .xml file usage, but I have not found a way to have multiple consecutive keys per line (without a line-break / whiste space inbetween them). What I have (python bits to reproduce them below): ---------------------------------------- <key>some value3</key> <string>some value5</string> ---------------------------------------- What I try to achieve: ---------------------------------------- <key>some value3</key><string>some value5</string> ---------------------------------------- If anyone has any pointers, that would be grand. Cheerio & all the best! c. ----------------------------------------------------- import lxml.etree import lxml.builder E = lxml.builder.ElementMaker() #dict & key syntax DICT = E.dict KEY = E.key TrackID = E.key Name = E.key Artist = E.key INTGR = E.integer STRNG = E.string DTE = E.date the_XML = DICT( DICT( KEY('2'), DICT( TrackID('some value1', INTGR('some value3')), #nested trees/keys Name('some value2'), STRNG('some value4'), #standard behaviour Artist('some value3'), STRNG('some value5'), # how to print this in a single line: <key>some value3</key><string>some value5</string> ), KEY('4'), ) ) print lxml.etree.tostring(the_XML, pretty_print=True)

2 1

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 March 2016