Mailman 3 November 2014 - 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

Generating code from schema
by Charlie Clark 29 Jan '15

29 Jan '15

Hi, just a quick question about what you can and cannot do with lxml's schema support. In openpyxl we're moving towards a 1:1 implementation of the underlying schema. lxml.objectify isn't directly an option for two reasons: lxml is an optional dependency and there are cases where we'd definitely run out of memory. Instead we're using descriptors to enforce type definitions. This means a little more code but now that it seems to be working well I was thinking whether we could automate some of the process. I've looked at some of the existing XSD to Python generators but the generated code is far from what I'd like to have. Can we use the lxml schema support for anything other than validation? ie. can I query a schema object for a particular definition? Or is the best approach to parse the XSD files directly and work through the definitions with a mapping? Charlie -- Charlie Clark Managing Director Clark Consulting & Research German Office Kronenstr. 27a Düsseldorf D- 40217 Tel: +49-211-600-3657 Mobile: +49-178-782-6226

4 13

XML Digital Signature (Xades)
by Ovnicraft 03 Jan '15

03 Jan '15

Hi to all ! Maybe this topic is off, but i want to comment here and get your feedback. I am working in digital signatures for my country and i want to work just in python, so my work start reading espec about xades[1], nothing complicated, now i see lxml can help me but i want to know if anyone here has experience around this. I have an example about xml file[2] and see basic x509 cert use and RSA key. Any comment are really appreciated ! Regards ! [1] http://www.w3.org/TR/XAdES/ [2] https://gist.github.com/ovnicraft/c8645904e01e0a071199 -- [image: Cristian Salamea on about.me] Cristian Salamea about.me/ovnicraft <http://about.me/ovnicraft>

2 3

Efficient incremental parsing using etree.iterparse
by D.H.J. Takken 24 Nov '14

24 Nov '14

Hello, I need to process very large XML files as quickly as possible. The XML processing does not require processing of every single tag, so I was looking at the iterparse method. Unfortunately, the iterparse method only allows one tag name to be specified for triggering events, while I need to do processing on two or three different tags. This would still be much more efficient than using the target parser method, because the XML data contains many more tags that do not require immediate processing. So, it looks like I need something in between processing *all* tags and processing a single tag. Is there any way to do that? Thanks for any hints!

3 5

christmas funding
by Stefan Behnel 21 Nov '14

21 Nov '14

Hi all, my bicycle was recently stolen and since I now have to get a new one, here's a proposal. >From today on until December 24th, I will divert all donations that I receive for my work on lxml to help in restoring my local mobility. If you do not like this 'misuse', do not donate in this time frame. I do hope, however, that some of you like the idea that the money they give for something they value is used for something that is of value to the receiver. All the best, Stefan

2 1

Re: [lxml] Efficient incremental parsing using etree.iterparse
by D.H.J. Takken 21 Nov '14

21 Nov '14

Ah wow, one of the hidden treasures of lxml.. :) Thanks! On 11/21/2014 12:58 PM, Steven Vereecken wrote: > Hello, > > It doesn't seem to be mentioned in the docs, but you *can* specify > multiple tag names (just use a list of names instead of one string). > I'm not really sure where I picked that up myself, maybe from this > mention in the changelog (features added in 3.0alpha1) : > "Tree iteration and iterparse() with a selective tag argument supports > passing a set of tags. Tree nodes will be returned by the iterators if > they match any of the tags." > > greetings, > Steven > > 2014-11-21 11:47 GMT+01:00 D.H.J. Takken <d.h.j.takken(a)xs4all.nl > <mailto:d.h.j.takken@xs4all.nl>>: > > Hello, > > I need to process very large XML files as quickly as possible. The XML > processing does not require processing of every single tag, so I was > looking at the iterparse method. > > Unfortunately, the iterparse method only allows one tag name to be > specified for triggering events, while I need to do processing on two or > three different tags. This would still be much more efficient than using > the target parser method, because the XML data contains many more tags > that do not require immediate processing. > > So, it looks like I need something in between processing *all* tags and > processing a single tag. Is there any way to do that? > > Thanks for any hints! > _________________________________________________________________ > Mailing list for the lxml Python XML toolkit - http://lxml.de/ > lxml(a)lxml.de <mailto:lxml@lxml.de> > https://mailman-mail5.webfaction.com/listinfo/lxml > >

2 2