lxml - The Python XML Toolkit June 2013

lxml@python.org

10 participants
15 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

lxml.objectify drops leading whitespace
by Wolfgang Schnerring 02 Oct '13

02 Oct '13

Hello, lxml.objectify drops leading whitespace before a tag: >>> lxml.etree.tostring(lxml.objectify.fromstring(' <a>foo</a>')) '<a>foo</a>' while lxml.etree handles the same situation just fine: >>> lxml.etree.tostring(lxml.etree.fromstring(' <a>foo</a>')) ' <a>foo</a>' What's the reason for the different behaviour? Is this intentional? Most importantly, how can I make lxml.objectify preserve whitespace correctly? Thanks for your help, Wolfgang

2 2

difference between fromstring() and XML()
by Ofer Nave 27 Jun '13

27 Jun '13

Just joined the list. Going to have some more interesting questions shortly, as I am about to try implementing my own parser target and object tree, but I'll start with something simple to make sure my list subscription is working. What is the difference between lxml.etree.XML() and lxml.etree.fromstring()? -ofer

4 5

How to tell XSLT processor not to remove CDATA
by zetah 24 Jun '13

24 Jun '13

Hi, please take a look at this code: ======================================== from lxml import etree parser = etree.XMLParser(strip_cdata=False) tree = etree.parse('sample_with_cdata.xml', parser) transform = etree.XSLT(etree.parse('dupe.xsl')) xml_out = transform(tree) xml_out.write('processed.xml') ======================================== Transformation removes CDATA from initial XML file. How can I tell XSLT processor to leave CDATA as is? TIA

1 1

findall difference unix vs windows.
by Tim Arnold 20 Jun '13

20 Jun '13

I don't know why my lxml differs between my FreeBSD and my Windows installation. This is what I get on FreeBSD and what I expected to get: Python 2.7.1 (r271:86832, Apr 5 2011, 13:19:14) [GCC 4.2.1 20070719 [FreeBSD]] on freebsd8 Type "help", "copyright", "credits" or "license" for more information. >>> from lxml import etree >>> tree = etree.parse('generic.xml') >>> xns = {'d': 'http://docbook.org/ns/docbook'} >>> tree.findall('//d:section', namespaces=xns) That returns a list of all the section elements. Help shows what I expected to see: >>> help(tree.findall) Help on built-in function findall: findall(...) findall(self, path, namespaces=None) But this, on windows 7, is not what I expected: C:\Windows\system32>python Python 2.7.2 (default, Jun 12 2011, 15:08:59) [MSC v.1500 32 bit (Intel)] on win32 Type "help", "copyright", "credits" or "license" for more information. >>> from lxml import etree >>> tree = etree.parse("e:/generic.xml") >>> xns = {'d': 'http://docbook.org/ns/docbook'} >>> tree.findall('//d:section', namespaces=xns) Traceback (most recent call last): File "<stdin>", line 1, in <module> TypeError: findall() takes no keyword arguments And help shows this: >>> help(tree.findall) Help on built-in function findall: findall(...) findall(self, path) Finds all elements matching the ElementPath expression. Same as getroot().findall(path). So have I done something wrong with my install? thanks, --Tim

2 1

Question regarding validating xml against multiple nested dtd's
by Dhulipala, Pradyot 19 Jun '13

19 Jun '13

Hi, I was wondering if it was possible to use lxml to validate against a DTD , which refers to other dtd's. ie: DOCTYPE within xml specifies the location of a DTD which then refers to other DTD's for its elements. thanks -Pradyot ________________________________ NOTICE: Morgan Stanley is not acting as a municipal advisor and the opinions or views contained herein are not intended to be, and do not constitute, advice within the meaning of Section 975 of the Dodd-Frank Wall Street Reform and Consumer Protection Act. If you have received this communication in error, please destroy all electronic and paper copies and notify the sender immediately. Mistransmission is not intended to waive confidentiality or privilege. Morgan Stanley reserves the right, to the extent permitted under applicable law, to monitor electronic communications. This message is subject to terms available at the following link: http://www.morganstanley.com/disclaimers If you cannot access these links, please notify us by reply message and we will send the contents to you. By messaging with Morgan Stanley you consent to the foregoing.

1 0

Possible bug in lxml.objectify
by Amaury Forgeot d'Arc 17 Jun '13

17 Jun '13

Hi, By doing the cffi port, I noticed this suspect line in lxml.objectify.pyx (line 1689): elif c_ns.prefix is not NULL or c_ns.prefix[0] != c'\0': It seems to me that the connector should be "and" instead, otherwise a prefix of "" would yield a typename starting with a colon character... I haven't tried though. But it looks like a bad negation of a similar statement above. -- Amaury Forgeot d'Arc

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 June 2013