Mailman 3 July 2011 - lxml - The Python XML Toolkit

[lxml-dev] lxml has its page on launchpad
by Stefan Behnel 11 Apr '23

11 Apr '23

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 10 Apr '23

10 Apr '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/>

6 6

[lxml-dev] Reparenting a node
by Lawrence Oluyede 30 Jan '23

30 Jan '23

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 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] 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-dev] confusing xpath performance characteristics
by jholg＠gmx.de 24 Aug '12

24 Aug '12

Hi, I ran into some performance characteristics of lxml/libxml2 xpath that I find rather confusing: I try to find the @type attribute of a certain element in an XML Schema (which contains lots of complexType definitions with lots of elements in them; unfortunately I can't post the schema): >>> timeit.Timer(stmt="""xpath(schema)""", setup="""from lxml import etree, objectify; schema=etree.parse('NDM.xsd').getroot(); xpath = etree.XPath('//xs:element[@name="equity"]/@type', namespaces={'xs': 'http://www.w3.org/2001/XMLSchema'})""").repeat(number=10) [0.095885038375854492, 0.096823930740356445, 0.096174955368041992] So I think I'm being smart and give a little more path information - reckoning that this should *improve* performance: >>> timeit.Timer(stmt="""xpath(schema)""", setup="""from lxml import etree, objectify; schema=etree.parse('NDM.xsd').getroot(); xpath = etree.XPath('/xs:schema//xs:element[@name="equity"]/@type', namespaces={'xs': 'http://www.w3.org/2001/XMLSchema'})""").repeat(number=10) [0.1770780086517334, 0.1775970458984375, 0.17748594284057617] Hm. Performance degrades slightly. I'm adding even more of the path to where my desired elements live in the schema: >>> timeit.Timer(stmt="""xpath(schema)""", setup="""from lxml import etree, objectify; schema=etree.parse('xsd/NDM.xsd').getroot(); xpath = etree.XPath('/xs:schema/xs:complexType//xs:element[@name="equity"]/@type', namespaces={'xs': 'http://www.w3.org/2001/XMLSchema'})""").repeat(number=10) [103.79744100570679, 103.83671712875366, 103.61817717552185] What??? >>> timeit.Timer(stmt="""xpath(schema)""", setup="""from lxml import etree, objectify; schema=etree.parse('/ae/data/pydev/hjoukl/NDM/SVN_CO/TRUNK/ndm/reference/xsd/NDM.xsd').getroot(); xpath = etree.XPath('/xs:schema/xs:complexType/*/xs:element[@name="equity"]/@type', namespaces={'xs': 'http://www.w3.org/2001/XMLSchema'})""").repeat(number=10) [0.044407129287719727, 0.044126987457275391, 0.044229030609130859] >>> Ok, this version's better than my naive approach, which seems logical to me. But why would '/xs:schema/xs:complexType//xs:element[@name="equity"]/@type' perform drastically slower than '/xs:schema/xs:complexType//xs:element[@name="equity"]/@type' ? libxml2 problem? Running the same xpaths in Oxygen I don't notice performance differences (can't profile this). Holger -- GRATIS für alle GMX-Mitglieder: Die maxdome Movie-FLAT! Jetzt freischalten unter http://portal.gmx.net/de/go/maxdome01

2 5

pypi still pointing to codespeak.net
by tomw 26 Jul '11

26 Jul '11

Hi, trying to install lxml via the python setuptools, pypi ist still pointing to codespeak.net which in consequence creates an error as codespeak isn't in operation any longer. best, -- tomw <tomw(a)ubilix.com>

2 2

[lxml-dev] Codespeak shutting down: migration plans?
by Luciano Ramalho 23 Jul '11

23 Jul '11

Dear colleagues, As a long-time user of lxml I was shocked to read a message today from Holger Krekel about the end of Codespeak (see full text at the end of this). First we need to thank Holger for all these years of free service. Then we need to quickly plan and execute a migration to some other repository. I am willing to help, but I am no core developer of lxml, and in fact this is my first message ever to this mailing list, so I think we need someone better known to this community to lead the migration effort. lxml as a key piece of the Python ecosystem and for the benefit of its present and future users and the wider Python community we need to make sure it continues to be available, and to make sure as many references (pypi!) as possible point to the new canonical repository. Finally, a big thank you to Martijn, Philikon, Stefan and all the others who have built this great piece of software. Cheers, -- Luciano Ramalho programador repentista || stand-up programmer Twitter: @luciano ######################################### hi codespeak.net users, (sorry if you get mail twice, i wanted to make sure ...) after 8 years of operation codespeak.net services are bound to terminate, starting END OF FEBRUARY 2011 Background: one of the original codespeak purposes was to offer subversion (then in version 0.17) for the PyPy and other projects but today this is not too interesting given the pletora of VCS hosting solutions. Also, there aren't too many admins besides me, the hosting is costing money, PyPy's repository has moved to Bitbucket and i am re-shuffling my priorities preparing for my soon to emerge father-hood. After February 2011 i probably won't be able to help much with any transition issues or questions. The host will keep on running for a while but i give no guaruantees. Some remarks regarding termination wrt to the FEB 2011 deadline: * the subversion repo will turn read-only (and will eventually be switched off). * Shell accounts will be restricted to those people who need it *and* mail me about it. Some time later they will be gone as well. * Mailing lists will be terminated as well unless i get a mail asking me to postpone termination for a specific time. You can go to your respective mailman admin page and extract a list of members. If you mail me i can also provide a list of members. * Any remaining web docs/pages will probably continue to exist for a while but i also prefer them to be moved away by end Feb 2011. Note that the codespeak svn repository contains a lot of projects. For migration you have two options: do a flat import just of your project checkout directory into a new version system. This is super-simple, obviously. If you want to preserve history for your project please mail me and i either provide you a full dump or a filtered dump only containing your project. So long and I hope you all had a good time and enjoyed the services and also have a good transition now. see you in other places, holger krekel _______________________________________________ codespeak-ann(a)codespeak.net http://codespeak.net/mailman/listinfo/codespeak-ann

4 7

Re: [lxml] (no subject)
by Stefan Behnel 22 Jul '11

22 Jul '11

schwehr(a)ccom.unh.edu, 21.07.2011 21:18: > I'm looking at how my I might add a little bit of functionality to the > PyKML library and learning the lxml objectify API at the same time. I've > been a light user (and fink packager for lxml) for quite a few years, but > I'm definitely a beginner at objectify. I'd like to be able to catch when > anything but a string is passed to a "GX.coord", I need to do the proper > conversion of a string (which is definitely not the same as the default > python behavior.) Below, I need to (if possible) catch a tuple or other > iteratable object and convert is to a space delimited string. e.g. > > (-120.223341,39.198288,1884.609) > or > [-120.223341,39.198288,1884.609] > > Would need to be converted to this: > > -120.223341 39.198288 1884.609 > > Is this possible to drop in a filter function or class?? > > > # http://code.google.com/p/pykml/ > > from pykml.factory import KML_ElementMaker as KML > from pykml.factory import GX_ElementMaker as GX > > multitrack = GX.MultTrack(id='ship_%d_multitrack' % mmsi) > for group_num, group in enumerate(groups): > > track = GX.Track(id='ship_%d_track_%d' % (mmsi, group_num) ) > > for pt in group: > when = datetime.datetime.utcfromtimestamp(pt['ts']) > track.append( KML.when( when ) ) > > for pt in group: > track.append( GX.coord( (pt['x'],pt['y'])) ) > > multitrack.append(track) There are two main options. 1) You can subtype the ElementMaker that is used in pykml.factory and override the ".coord()" method explicitly. 2) You can register a PyType in lxml.objectify that handles types, lists, etc., either specifically for the "coord" tag or always. That's the more general and proper way, and it also allows you to get a tuple back when you read the value of such an XML tag. http://lxml.de/objectify.html#how-data-types-are-matched http://lxml.de/objectify.html#defining-additional-data-classes You may want to integrate this feature into pykml itself, BTW, the authors may be happy about a patch. Have you talked to them? Stefan

4 3

tab(\t) in the attrib will be replaced by a space
by BearXu 22 Jul '11

22 Jul '11

Any one meets the same problem? >>> from lxml import etree >>> doc = etree.fromstring("<n text='a\tb' />") >>> doc <Element n at 0x1eb9bc0> >>> doc.attrib {'text': 'a b'} >>> doc.attrib['text'] == "a\tb" False

2 1