lxml - The Python XML Toolkit December 2006

lxml@python.org

17 participants
15 discussions

[lxml-dev] pretty-printing
by Albert Brandl 24 Feb '07

24 Feb '07

Hi! I've posted a question about pretty-printing some time ago. Now I finally found the time to construct an example. The problem occurs with the following code: nsmap = dict (foo="http://foo.org", bar = "http://bar.org") e = Element("{http://foo.org}somefoo", nsmap = nsmap) s = Element("{http://bar.org}somebar", nsmap = nsmap) e.append(s1) et = ElementTree(e) et.write("foo.xml", pretty_print = True) This code creates the following XML file: <foo:somefoo xmlns:foo="http://foo.org" xmlns:bar="http://bar.org"> <bar:somebar xmlns:foo="http://foo.org" xmlns:bar="http://bar.org"/> </foo:somefoo> The problem is that "bar:somebar" redundantly declares the namespaces for "foo" and "bar", which affects both the readability and the size of the XML file. If the element "s" is appended to "e" by using the SubElement function instead of "append", the content of the XML file looks like I'd expect: <foo:somefoo xmlns:foo="http://foo.org" xmlns:bar="http://bar.org"> <bar:somebar/> </foo:somefoo> Is this a known bug? Thanks & best regards, Albert Brandl

4 5

[lxml-dev] [objectify] __MATCH_PATH_SEGMENT regex modification suggestion
by Holger Joukl 02 Jan '07

02 Jan '07

Hi, I suggest to loosen the __MATCH_PATH_SEGMENT regex a little to care for more possible element names, which are sometimes outside of my control. Currently ObjectPath chokes on paths like 'root.a-x.a-y'. While such names are often inconvenient at best I found that python itself is quite non-restrictive wrt attibute names: python2.4 Python 2.4.3 (#2, Nov 20 2006, 16:26:48) [GCC 2.95.2 19991024 (release)] on sunos5 Type "help", "copyright", "credits" or "license" for more information. >>> class Foo(object): ... pass ... >>> setattr(Foo, 'a-b', "hmm") >>> Hence, I propose to change the regex to: cdef object __MATCH_PATH_SEGMENT __MATCH_PATH_SEGMENT = re.compile( r"(\.?)\s*(?:\{([^}]*)\})?\s*([^.{}]+)\s*(?:\[\s*([-0-9]+)\s*\])?", re.U).match (Changed: ([^.{}]+) replaces (\w+)) Holger Der Inhalt dieser E-Mail ist vertraulich. Falls Sie nicht der angegebene Empfänger sind oder falls diese E-Mail irrtümlich an Sie adressiert wurde, verständigen Sie bitte den Absender sofort und löschen Sie die E-Mail sodann. Das unerlaubte Kopieren sowie die unbefugte Übermittlung sind nicht gestattet. Die Sicherheit von Übermittlungen per E-Mail kann nicht garantiert werden. Falls Sie eine Bestätigung wünschen, fordern Sie bitte den Inhalt der E-Mail als Hardcopy an. The contents of this e-mail are confidential. If you are not the named addressee or if this transmission has been addressed to you in error, please notify the sender immediately and then delete this e-mail. Any unauthorized copying and transmission is forbidden. E-Mail transmission cannot be guaranteed to be secure. If verification is required, please request a hard copy version.

1 1

[lxml-dev] lxml on OS X compile problems
by Matt 30 Dec '06

30 Dec '06

Hi All, My first question - anyone successfully build lxml on OS X 10.3.9? And next, have they encoutnered the following error - specifics- OS X 10.3.9 gcc 3.3 python 2.4.4 lxml 1.1.2 libxml2 config line - ./configure \ --with-python=/Library/Frameworks/Python.framework/Versions/2.4/ libxslt config line- ./configure \ --with-python=/Library/Frameworks/Python.framework/Versions/2.4/ \ --prefix=/usr/local \ --with-libxml-prefix=/usr/local \ --with-libxml-include-prefix=/usr/local/include \ --with-libxml-libs-prefix=/usr/local/lib Results- xsltproc was compiled against libxml 20611, libxslt 10109 and libexslt 807 libxslt 10117 was compiled against libxml 20626 libexslt 807 was compiled against libxml 20611 I'm a little worried that the xsltproc wasn't combiled against the same libraries- but I'm not sure how to resolve this. I've played with installing various versions of libxslt and libxml and they seem to be installing- though all the libxml2 headers may not be installing properly. The present error occurs since I've copied the missing headers xmlstring.hand xlmsave.h to /usr/include/<etc>. Using Pyrex to create the objectify.c file doesn't help. >python setup.py install Building lxml version 1.2.dev-35415 running install running bdist_egg running egg_info writing src/lxml.egg-info/PKG-INFO writing top-level names to src/lxml.egg-info/top_level.txt writing dependency_links to src/lxml.egg-info/dependency_links.txt reading manifest template 'MANIFEST.in' warning: no files found matching 'objectify.c' under directory 'src/lxml' warning: no files found matching '*.html' under directory 'doc' warning: no files found matching '*.py' under directory 'Pyrex' writing manifest file 'src/lxml.egg-info/SOURCES.txt' installing library code to build/bdist.macosx-10.3-ppc/egg running install_lib running build_py running build_ext building 'lxml.etree' extension gcc -fno-strict-aliasing -Wno-long-double -no-cpp-precomp -mno-fused-madd -fno-common -dynamic -DNDEBUG -g -O3 -I/usr/include/libxml2 -I/Library/Frameworks/Python.framework/Versions/2.4/include/python2.4 -c src/lxml/etree.c -o build/temp.macosx-10.3-ppc-2.4/src/lxml/etree.o -w In file included from src/lxml/etree.c:27: /usr/include/libxml2/libxml/xmlstring.h:28: error: redefinition of `xmlChar' /usr/include/libxml2/libxml/tree.h:107: error: `xmlChar' previously declared here /usr/include/libxml2/libxml/xmlstring.h:40: error: syntax error before "xmlChar" /usr/include/libxml2/libxml/xmlstring.h:41: error: parse error before "xmlStrdup" <... and much more ...> Any hints? Thanks for your time, Matt

1 0

[lxml-dev] relax ng bug: validation twice doesn't give same answer
by Martijn Faassen 21 Dec '06

21 Dec '06

Hi there, We just ran into the following problem with lxml's RelaxNG validation. Validating with the same RelaxNG schema gives the right result (invalid). Validating again however gives valid! This script is a minimal test case that demonstrates the problem. Tested with lxml 1.1.2 and libxml2 2.6.24 and also 2.6.26 on another machine. From an earlier thread last year it's possible that this is a libxml2 bug: http://codespeak.net/pipermail/lxml-dev/2005-September/000423.html This was more than a year ago though and it's somewhat surprising this still wasn't fixed. I found the bug report: http://bugzilla.gnome.org/show_bug.cgi?id=315883 and have added something to it in the hope it'll spur some activity in confirming it... Regards, Martijn from lxml import etree from StringIO import StringIO v = etree.RelaxNG(etree.parse(StringIO('''\ <?xml version="1.0" encoding="UTF-8"?> <grammar ns="http://some.namespace.org" xmlns="http://relaxng.org/ns/structure/1.0"> <start> <element name="root"> <element name="sub"><text/></element> </element> </start> </grammar> '''))) # this is an invalid document d = etree.parse(StringIO('''\ <root xmlns="http://some.namespace.org"> <sub><something /></sub> </root>''')) first = v.validate(d) # returns 0, what is expected second = v.validate(d) # returns 1! assert first == second, "Validity isn't the same over time"

1 0

[lxml-dev] Processing instruction doubt
by Steve Howe 20 Dec '06

20 Dec '06

Hello all, This should be rather a stupid question, but supposing I have an ElementTree instance, and I want to add a processing instruction to it - in my case, a xml-stylesheet PI - how do I add that PI in the correct location of the tree (i.e. before the root) without serializing ? <?xml-stylesheet type="text/xsl" href="stylesheet.xsl"> <data> ... </data> Before someone answers "add the PI into the XSLT before serializing it", the ElementTree is received by a function from an end user and I have no control over what's received. Thanks. -- Best Regards, Steve Howe

1 0

[lxml-dev] lxml documentation volunteers?
by Martijn Faassen 19 Dec '06

19 Dec '06

Hi there, I think it's time to give the lxml documentation a reworking, in particular our API documentation. It must become more clear for users what is in the API; I find myself having to look at the code or do a dir() far too often to find whether a feature is supported. What I would wish for is API documentation similar to the module documentation on python.org. Something close to that would be familiar for users so they can get started with lxml quickly. I hope we can also continue to doctest code samples in the documentation. For completeness I think we would need to integrate the existing ElementTree API documentation so we have a one-stop-shop for people using lxml, instead of the scattered situation now. We should mark where an API is taken from ElementTree so that people can easily write compatible code. Such API documentation would also help us identify possible ElementTree APIs we haven't implemented yet, and it might also suggest APIs we want to imply that are currently missing. Any volunteers for this work? Regards, Martijn

1 0

[lxml-dev] lxml segfaults while instantiating ElementBase
by Marian Schubert 19 Dec '06

19 Dec '06

Hello, i guess it should not be instantiated but still... Python 2.4.4 (#2, Oct 20 2006, 00:23:25) [GCC 4.1.2 20061015 (prerelease) (Debian 4.1.1-16.1)] on linux2 >>> from lxml.etree import ElementBase >>> ElementBase() Segmentation fault lxml.etree: (1, 1, 1, 0) libxml used: (2, 6, 27) libxml compiled: (2, 6, 26) libxslt used: (1, 1, 18) libxslt compiled: (1, 1, 17) cu, Maio

2 1

[lxml-dev] jbrout fails to work second time on Fedora Core 6/RHEL 5b2
by Matej Cepl 15 Dec '06

15 Dec '06

Hi, trying to package jbrout (photo management application) for Fedora Extras and I get always this error when running jbrout for the second time (this time on RHEL 5beta2; verision of python-lxml is still just 1.0.3.2): [matej@hubmaier ~]$ jbrout GTK Accessibility Module initialized Traceback (most recent call last): File "/usr/share/jbrout/jbrout.py", line 2164, in ? main() File "/usr/share/jbrout/jbrout.py", line 2133, in main JBrout.init(canModify) File "/usr/share/jbrout/db.py", line 1297, in init JBrout.db = DBPhotos( JBrout.getConfFile("db.xml") ) File "/usr/share/jbrout/db.py", line 118, in __init__ self.root = ElementTree(file=file).getroot() File "etree.pyx", line 1504, in etree.ElementTree File "parser.pxi", line 687, in etree._parseDocument File "parser.pxi", line 624, in etree._parseDocFromFile File "parser.pxi", line 364, in etree._BaseParser._parseDocFromFile File "parser.pxi", line 432, in etree._handleParseResult File "parser.pxi", line 403, in etree._raiseParseError etree.XMLSyntaxError: line 1: PCDATA invalid Char value 2 [matej@hubmaier ~]$ Further discussion of this bug is on jbrout list at http://groups.google.com/group/jbrout/browse_thread/thread/73aaa54115930c5b Could anybody help me how to make this package work? Thanks a lot, Matěj -- http://www.ceplovi.cz/matej/blog/, Jabber: ceplma<at>jabber.cz GPG Finger: 89EF 4BC6 288A BF43 1BAB 25C3 E09F EF25 D964 84AC My life has been full of terrible misfortunes most of which never happened. -- Michel de Montaigne

3 2

[lxml-dev] About lxml status
by David Soulayrol 14 Dec '06

14 Dec '06

Hello, I am currently using 4Suite-XML for a project on my own, which makes use of DOM, XSLT and XPath. I've always looked around if I could find other libraries to replace 4Suite eventually, and I (re-) discovered libxml today, and found a link to lxml from there. What I'd like to know is (before I dive deeply in documentation) how you would compare the XML support between 4Suite and lxml. Would you say lxml is ready for common DOM manipulations, XSLT transformations and simple XPath usage ? I ask this because I've read in http://xmlsoft.org/index.html: "Document Object Model (DOM) http://www.w3.org/TR/DOM-Level-2-Core/ the document model, but it doesn't implement the API itself, gdome2 does this on top of libxml2" 'Hope I was not offending :) Thanks, -- David.

7 12

Re: [lxml-dev] redundant namespace declarations
by Albert Brandl 06 Dec '06

06 Dec '06

Hi, On Mon, Dec 04, 2006 at 06:44:28PM +0100, Stefan Behnel wrote: > > Well, maybe that won't be that soon. It's currently undecided if this will be > in the next release, so it will stay out of the trunk for now. No problem. I've adapted the code responsible for building the element tree to use SubElement instead of append, so that "pretty_print = True" does what I want. A minor problem remains, but I have a workaround for this. If you try to write the document to a file without write access, "write_c14n" raises a C14NError: >>> from lxml.etree import * >>> et = ElementTree(Element("abc")) >>> et.write_c14n("nonwritable.xml") >>> et.write_c14n("notwritable.xml") Traceback (most recent call last): File "<stdin>", line 1, in ? File "etree.pyx", line 657, in etree._ElementTree.write_c14n File "serializer.pxi", line 224, in etree._tofilelikeC14N etree.C14NError: C14N failed But if you use "write" instead, lxml silently ignores the fact that the file can't be written: >>> et.write("notwritable.xml") >>> For now, I'm just writing to a StringIO buffer and open the file manually, so this is no serious problem for me. But others might well be bitten by this bug, even more so since lxml does not give any feedback about what just happened. Best regards, Albert Brandl

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 December 2006