Mailman 3 September 2013 - 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.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

Is there a way to add a resolver to a programmatically constructed XML? [DISREGARD]
by Mikhail Edoshin 30 Sep '13

30 Sep '13

Please disregard the previous message about not begin able to resolve URLs from a programmatically constructed XML; everything works, the problem was in URLs themselves: they were paths with Windows path separators and when I changed these to slashes, everything started to work. Kind regards, Mikhail

1 0

Is there a way to add a resolver to a programmatically constructed XML?
by Mikhail Edoshin 29 Sep '13

29 Sep '13

Hi, Is there a way to add a resolver to a programmatically constructed XML? I have a such a document and I want to apply a XSLT to it; the problem is that the document has links to other documents and there's no way to resolve them, because the document has never been parsed and thus doesn't remember its parser and the parser's resolvers. Kind regards, Mikhail

1 0

Problems with XSLT extensions
by Mikhail Edoshin 29 Sep '13

29 Sep '13

Hi, I'm Mikhail Edoshin and this is my first post to the list. I'm trying to write a few XSLT Extension element for various purposes and I'm not quite sure if the behavior I'm observing is expected or I should submit a bug request. Please help. Here's the situation: I want to write an element to create a directory, e.g.: <path:make-directory target="{$target}" /> The $target variable is supposed to be defined by the XSLT processor. The problem is that I cannot evaluate this expression or have it evaluated with apply_templates() or something like. Here's what I've tried: 1. First, I can have it evaluated if I provide a child element and use process_children(): <path:make-directory> <target value="{$target}" /> </path:make-directory> This construction works perfectly and for now I'm using it, but it's less elegant, of course, than having it in an attribute. 2. I see that XPaths do not work with self_node or input_node, but I don't quite understand why. I realize these elements are read-only, but applying an XPath isn't going to change them, is it? Besides, it seems that I can use context.context_node, which is same as input_node, but is not read-only and thus can run any XPath or whatever. This is good to have, although in my case it doesn't help, because I'd like to evaluate a XSLT variable. 3. For the remaining tests I prepared the following example: <path:make-directory> <xsl:text>sample text</xsl:text> <xsl:value-of select="$target" /> </path:make-directory> - If I use process_children(), it evaluates as expected: 'sample text', then the value of $target. - If I try to apply_templates() to the extension itself, I only get 'sample text'. - If I try to apply_templates() to each child element alone (using 'for item in self_node') I seem to a) skip the <xsl:text> element and b) I get no result. (From what I understand <xsl:text> is probably translated directly to text content (text or tail); if so, it's OK, as I'm more concerned about missing xsl:value-of.) - If I try to create a new xsl:text and apply_templates() to it, I get the text content of the element. - If I try to create a new xsl:value-of and apply_templates() to it, I get no result. - If I try to create an arbitrary element (with sub-elements, etc.) and apply_templates() to it, I only get element texts, if any; if there's no text, I get nothing. - Also, if I try to run process_children() without output_node, I get an error: TypeError: invalid argument type <type 'NoneType'> So, basically, what seems to be wrong is that: - XPaths do not work with self_node and input_node. - apply_templates() only adds text content, not elements or attributes. - process_children() does not accept None for output_element (contrary to the documentation). The two latter sound like bugs to me, but I'm not sure about the XPath limitation. Kind regards, Mikhail

1 0

In-place modification of .xpath() results (doesn't work!!1)
by Paul Sokolovsky 15 Sep '13

15 Sep '13

Hello, This wonderful Sunday morning, I decided to write small hack tool, just to be frustrated by the following code not working: target = tree.xpath("target[@name='-package-resources']")[0] aapt = target.xpath("//aapt")[0] aapt.set("manifestpackage", "foo.bar") print lxml.etree.tostring(target) I checked that element in aapt is modified as expected, but the changes are not mirrored in target. Digging further with print target.getchildren()[1].getchildren() print aapt I see that original element and one returned by .xpath() are different: [<Element aapt at 0x957134c>] <Element aapt at 0x9571374> Moreover, the original XML element contains comments, while one returned by .xpath() does not. Why all this doesn't work as intuitively expected? What's more strange is that I used pattern as above many times previously, and everything worked (the documents on which it worked definitely didn't have comments though). For reference, culprit XML is Android ant build.xml excerpt: <target name="-package-resources" depends="-crunch">  <do-only-if-not-library elseText="Library project: do not package resources..."> <aapt executable="${aapt}" command="package" versioncode="${version.code}" versionname="${version.name}" debug="${build.is.packaging.debug}" manifest="${out.manifest.abs.file}" assets="${asset.absolute.dir}" androidjar="${project.target.android.jar}" apkfolder="${out.absolute.dir}" nocrunch="${build.packaging.nocrunch}" resourcefilename="${resource.package.file.name}" resourcefilter="${aapt.resource.filter}" libraryResFolderPathRefid="project.library.res.folder.path" libraryPackagesRefid="project.library.packages" libraryRFileRefid="project.library.bin.r.file.path" previousBuildType="${build.last.target}" buildType="${build.target}" ignoreAssets="${aapt.ignore.assets}"> <res path="${out.res.absolute.dir}"/> <res path="${resource.absolute.dir}"/>   </aapt> </do-only-if-not-library> </target> -- Best regards, Paul mailto:pmiscml@gmail.com

2 2