Mailman 3 May 2012 - lxml - The Python XML Toolkit

objectify.parse() returns lxml.etree._ElementTree instead of lxml.objectify.ObjectifiedElement
by Roger Hoover June 4, 2012

June 4, 2012

Hi, Any idea why objectify.parse() is returning an lxml.etree._ElementTree object while objectify.parsestring() returns lxml.objectify.ObjectifiedElement? I've installed lxml 2.3.4 using easy_install on Ubuntu 10.04. from lxml import objectify import StringIO obj = objectify.parse(StringIO.StringIO("<foo><bar>1</bar></foo>")) print type(obj) #prints <type 'lxml.etree._ElementTree'> Thanks, Roger

2 2

xml install problems
by William Herry June 3, 2012

June 3, 2012

Hi, I am try to install xml on centos6.2 with command: pip-python install xml==2.3 it gives me this error: Downloading/unpacking lxml==2.3 Running setup.py egg_info for package lxml Building lxml version 2.3. Building with Cython 0.14.1. Using build configuration of libxslt 1.1.26 Building against libxml2/libxslt in the following directory: /usr/lib64 Installing collected packages: lxml Running setup.py install for lxml Building lxml version 2.3. Building with Cython 0.14.1. Using build configuration of libxslt 1.1.26 Building against libxml2/libxslt in the following directory: /usr/lib64 building 'lxml.etree' extension gcc -pthread -fno-strict-aliasing -O2 -g -pipe -Wall -Wp,-D_FORTIFY_SOURCE=2 -fexceptions -fstack-protector --param=ssp-buffer-size=4 -m64 -mtune=generic -D_GNU_SOURCE -fPIC -fwrapv -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 -fwrapv -fPIC -I/usr/include/libxml2 -I/usr/include/python2.6 -c src/lxml/lxml.etree.c -o build/temp.linux-x86_64-2.6/src/lxml/lxml.etree.o -w {standard input}: Assembler messages: {standard input}:150508: Warning: end of file not at end of a line; newline inserted gcc: Internal error: Killed (program cc1) Please submit a full bug report. See <http://bugzilla.redhat.com/bugzilla> for instructions. error: command 'gcc' failed with exit status 1 Complete output from command /usr/bin/python -c "import setuptools;__file__='/root/build/lxml/setup.py';execfile(__file__)" install --single-version-externally-managed --record /tmp/pip-g_IvOB-record/install-record.txt: Building lxml version 2.3. Building with Cython 0.14.1. Using build configuration of libxslt 1.1.26 Building against libxml2/libxslt in the following directory: /usr/lib64 running install running build running build_py running build_ext building 'lxml.etree' extension gcc -pthread -fno-strict-aliasing -O2 -g -pipe -Wall -Wp,-D_FORTIFY_SOURCE=2 -fexceptions -fstack-protector --param=ssp-buffer-size=4 -m64 -mtune=generic -D_GNU_SOURCE -fPIC -fwrapv -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 -fwrapv -fPIC -I/usr/include/libxml2 -I/usr/include/python2.6 -c src/lxml/lxml.etree.c -o build/temp.linux-x86_64-2.6/src/lxml/lxml.etree.o -w {standard input}: Assembler messages: {standard input}:150508: Warning: end of file not at end of a line; newline inserted gcc: Internal error: Killed (program cc1) Please submit a full bug report. See <http://bugzilla.redhat.com/bugzilla> for instructions. error: command 'gcc' failed with exit status 1 ---------------------------------------- Command /usr/bin/python -c "import setuptools;__file__='/root/build/lxml/setup.py';execfile(__file__)" install --single-version-externally-managed --record /tmp/pip-g_IvOB-record/install-record.txt failed with error code 1 Storing complete log in /root/.pip/pip.log I already installed libxml2-devel and libxslt-devel, can some body tell me what's going on? thanks in adv Regards -- =========================== William Herry WilliamHerryChina(a)Gmail.com

2 2

lxml.get_include() does not return system libxml paths
by Giovanni Bajo June 1, 2012

June 1, 2012

Hi Stefan, we submitted a patch (that is currently sitting in git trunk) for distributing pxd interface files with lxml (including the static Windows package), to simplify writing cython code that class the lxml Cython API interface. Unfortunately, we're not quite there yet, because lxml.get_include() still does not return the system include path for libxml (/usr/include/libxml2 or the like), in the cases in which the system ones were used (I think it does work in the case where libxml header files are being shipped within the lxml static package, like on Windows; I can't verify since there is no static Windows package for 2.4 yet). This means that each and every users of the lxml Cython API must include a build system that duplicates lxml's one build system and finds the system libxml include path. I was trying to get to a point where a lxml Cython API user should only call lxml.get_include() and get a list of pxd/h directories to be used for both cythoning (pxd) and compiling (h) the extension. Do you think it makes sense to get there? Thanks! -- Giovanni Bajo :: rasky(a)develer.com Develer S.r.l. :: http://www.develer.com My Blog: http://giovanni.bajo.it

2 1

gpx tostring for xml newbe
by janwillem June 1, 2012

June 1, 2012

I wanted to do some analyzing of Garmin gpx track and waypoint files. So I thought of diving into lxml and start with pretty printing a garmin file. Garmin writes all info on a single line which is not pretty. When split into lines a waypoint looks like: <wpt lat="52.151006" lon="15.373755"> <ele>14.742697</ele> <time>2012-05-19T20:23:15Z</time> <name>Gazon</name> <sym>Park</sym> <extensions> <wptx1:WaypointExtension> <wptx1:Samples>3</wptx1:Samples> </wptx1:WaypointExtension> </extensions> </wpt> when I do: wpt = '{%s}wpt' % xmlns waypoints = root.findall(wpt) for point in waypoints: print point.get('lon'), point.get('lat') print etree.tostring(point, pretty_print=True, with_tail=False) I get a lot of info from the beginning of the file between "<wpt" and "lat=". <wpt xmlns="http://www.topografix.com/GPX/1/1" xmlns:gpxx="http://www.garmin.com/xmlschemas/GpxExtensions/v3" xmlns:wptx1="http://www.garmin.com/xmlschemas/WaypointExtension/v1" xmlns:gpxtpx="http://www.garmin.com/xmlschemas/TrackPointExtension/v1" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" lat="52.151006" lon="15.373755"> <ele>14.742697</ele> <time>2012-05-19T20:23:15Z</time> <name>Gazon</name> <sym>Park</sym> <extensions> <wptx1:WaypointExtension> <wptx1:Samples>3</wptx1:Samples> </wptx1:WaypointExtension> </extensions> </wpt> Why is that and how to avoid? Thanks for helping this xml and lxml newbe, Janwillem

2 1

Re-announcing SOX: Sequential Output of XML
by John W. Shipman May 18, 2012

May 18, 2012

A correspondent has kindly pointed out that the Creative Commons BY-NC-ND license does not allow anyone to actually use this module. I've changed the license to BY-NC. John Shipman (john(a)nmt.edu), Applications Specialist New Mexico Tech Computer Center, Speare 146, Socorro, NM 87801 (575) 835-5735, http://www.nmt.edu/~john ``Let's go outside and commiserate with nature.'' --Dave Farber ---------- Forwarded message ---------- Date: Thu, 17 May 2012 21:06:05 -0600 (MDT) From: John W. Shipman <john(a)nmt.edu> To: lxml-dev <lxml(a)lxml.de> Cc: John Shipman <john(a)nmt.edu> Subject: Announcing SOX: Sequential Output of XML My CGI script that generates a huge XHTML table has been running into storage limitations because it uses lxml to build the table. So I build a Python module that applications can use to generate any XML content as a stream, so you can generate arbitrarily large XML files with a trivial amount of storage: http://www.nmt.edu/tcc/projects/sox/ Features: - Like Fredrik Lundh's builder.py module, it takes very little code to generate a lot of XML. If you're unfamiliar with this little gem, see here: http://effbot.org/zone/element-builder.htm - The module insures that every start tag has a matching end tag. Feel free to try this package out (Creative Commons BY-NC-ND license). I would greatly appreciate any feedback. Best regards, John Shipman (john(a)nmt.edu), Applications Specialist New Mexico Tech Computer Center, Speare 146, Socorro, NM 87801 (575) 835-5735, http://www.nmt.edu/~john ``Let's go outside and commiserate with nature.'' --Dave Farber

1 0

Announcing SOX: Sequential Output of XML
by John W. Shipman May 18, 2012

May 18, 2012

My CGI script that generates a huge XHTML table has been running into storage limitations because it uses lxml to build the table. So I build a Python module that applications can use to generate any XML content as a stream, so you can generate arbitrarily large XML files with a trivial amount of storage: http://www.nmt.edu/tcc/projects/sox/ Features: - Like Fredrik Lundh's builder.py module, it takes very little code to generate a lot of XML. If you're unfamiliar with this little gem, see here: http://effbot.org/zone/element-builder.htm - The module insures that every start tag has a matching end tag. Feel free to try this package out (Creative Commons BY-NC-ND license). I would greatly appreciate any feedback. Best regards, John Shipman (john(a)nmt.edu), Applications Specialist New Mexico Tech Computer Center, Speare 146, Socorro, NM 87801 (575) 835-5735, http://www.nmt.edu/~john ``Let's go outside and commiserate with nature.'' --Dave Farber

3 2

Custom XPath functions and "self" (or ".")
by Phillip B Oldham May 12, 2012

May 12, 2012

If I create a custom XPath function and use it in my XSL sheet using `self`, `self::node()`, `.` or `current()` as the nodeset passed in, for example: <xsl:if test="custom:my-func(.)">... ... the list of nodes is empty within the XPath function. If I use the name of the node referenced by `self` then everything works as expected and a list of nodes is passed into the function. I've created a testcase to explain better than I can in an email: http://pastebin.com/5jkBhRSD Is this the expected behaviour? -- Phillip B Oldham phillip.oldham(a)gmail.com +44 (0) 7525 01 09 01

1 0

Better error messages from XSL translations?
by Phillip B Oldham May 12, 2012

May 12, 2012

Is there any way to get better error messages when performing XSL translations? For instance, a line number or even a specific filename? -- Phillip B Oldham phillip.oldham(a)gmail.com +44 (0) 7525 01 09 01

2 2

Future of XSL-FO (fwd)
by John W. Shipman May 10, 2012

May 10, 2012

Sorry, sent this one to the old lxml mailing list. John Shipman (john(a)nmt.edu), Applications Specialist New Mexico Tech Computer Center, Speare 146, Socorro, NM 87801 (575) 835-5735, http://www.nmt.edu/~john ``Let's go outside and commiserate with nature.'' --Dave Farber ---------- Forwarded message ---------- Date: Wed, 9 May 2012 11:51:00 -0600 (MDT) From: John W. Shipman <john(a)nmt.edu> To: Carlos Araya <carlos.araya(a)gmail.com> Cc: lxml-dev <lxml-dev(a)codespeak.net>, docbook-apps mailing list <docbook-apps(a)lists.oasis-open.org> Subject: Future of XSL-FO On Tue, 8 May 2012, Carlos Araya wrote: +-- | Just curious as to why you think xsl-fo is a dead standard? +-- A colleague (who does not wish to be quoted) says there's not much action on the committee anymore. Although it is still officially supported, it seems moribund. I was sort of hoping that the committee was working on adding critical features not in the current standard that modern book designers appreciate, e.g., constraints about positioning content on facing pages, or text floated on both sides of a figure, or a page model not as primitive as the five-region simple-page-master model. Apparently not. I've heard a few people over the past few years insisting that the replacement for XSL-FO (within W3C) is to use the "@media print" feature of the CSS standard. If I read that correctly, that means that in order most ordinary people to get a decent print rendering of their web page, the following must hold: (1) The page author has to write the CSS to define how to render it on a fixed page size; (2) Their browser supports the "@media print" rule and renders it correctly. Then the user prints it using the browser's print function. Am I right? Is this practical? Do browsers do the right thing? Will this eventually obviate the need for XSL-FO? What replaces the Modular Style Sheets in my DocBook toolchain? What about the important differences between Web and print rendering? Will there be a table of contents? Will that and cross-references display page numbers instead of useless, unclickable underlining? How does that work in CSS? One of my pet peeves is Web pages that can't be printed because they contain program source code with lines way too wide to fit on the page. Will CSS render such pages with the pages wrapped and not truncated? If they do, will I be able to tell the hard line breaks from cases where the line got wrapped? Best regards, John Shipman (john(a)nmt.edu), Applications Specialist New Mexico Tech Computer Center, Speare 146, Socorro, NM 87801 (575) 835-5735, http://www.nmt.edu/~john ``Let's go outside and commiserate with nature.'' --Dave Farber

3 2

xslt timeout problem (lxml 2.3.4)
by Eric Sagnes May 7, 2012

May 7, 2012

Hello, I am developping a web application where I use the xslt component of lxml. >From the 2.3.4 of version of lxml, when I try to refresh a page I get no response till a timeout (infinite loop?). First, the system infos: -- Python : sys.version_info(major=2, minor=7, micro=3, releaselevel='final', serial=0) lxml.etree : (2, 3, 4, 0) libxml used : (2, 7, 8) libxml compiled : (2, 7, 8) libxslt used : (1, 1, 26) libxslt compiled : (1, 1, 26) -- The code -- ... parser = etree.XMLParser( no_network=False ) xslt_tree = etree.parse( StringIO.StringIO(contents.XSLT.generate(template_file)), parser ) transform = etree.XSLT( xslt_tree ) rdf_tree = etree.parse( rdf_file, parser ) ... -- The xslt generated by "StringIO.StringIO(contents.XSLT.generate(template_file))" contains url based includes as below: -- <xsl:include href="http://example.org/xslt/xhtml/parts/footer.xsl" /> -- When I remove all the includes from my xslt the request works well, so my guess is that there might be a problem with using url based xsl:include. Commenting out the "transform = etree.XSLT( xslt_tree )" line also make the request complete (with an error), so I guess it is where something happens. The code is working fine as it is with lxml 2.3.3. Is there a problem with this code? (eg, a setting I have to pass to etree.XMLParser) Thanks in advance, Eric

1 0