http://permalink.gmane.org/gmane.comp.python.lxml.devel hourly 1 1901-01-01T00:00+00:00 http://gmane.org/img/gmane-25t.png http://gmane.org http://permalink.gmane.org/gmane.comp.python.lxml.devel/3830 Hi (and sorry for the stupidly long subject, but otherwise it doesn't actually cover the subject), I'm not sure whether this is a bug or not (if not, there probably ought to be some note in the docs), but, for example: >>> from lxml import etree >>> foo = etree.fromstring("<root><a><b/></a><a/></root>") >>> for element in foo.iter(etree.Element): ... print element.tag ... if element.tag == "a": ... element.getparent().remove(element) ... root a b >>> foo = etree.fromstring("<root><a/><a/></root>") >>> for element in foo.iter(etree.Element): ... print element.tag ... if element.tag == "a": ... element.getparent().remove(element) ... root a a Only in the latter case does the final a element actually appear in the iteration, whereas in the former case it just vanishes. What changes the behaviour is the fact that in former case the first a element has a child: an empty b element. -- Geoffrey Sneddon <http://gsnedders.com/> Geoffrey Sneddon 2008-07-05T18:13:43 http://permalink.gmane.org/gmane.comp.python.lxml.devel/3829 On 5 Jul 2008, at 15:38, John W. Shipman wrote: Ah, simply that. Much thanks. -- Geoffrey Sneddon <http://gsnedders.com/> Geoffrey Sneddon 2008-07-05T14:51:19 http://permalink.gmane.org/gmane.comp.python.lxml.devel/3828 '<gi a1="one" a2="two"/>' '<gi a1="one"/>' Best regards, John Shipman (john< at >nmt.edu), Applications Specialist, NM Tech Computer Center, Speare 119, Socorro, NM 87801, (505) 835-5950, http://www.nmt.edu/~john ``Let's go outside and commiserate with nature.'' --Dave Farber John W. Shipman 2008-07-05T14:38:25 http://permalink.gmane.org/gmane.comp.python.lxml.devel/3827 Hi, I can't seem to find any way to totally remove an attribute, short of using Element.clear() (which has obvious issues when you just want to remove a single attribute). I need to remove at least < at >id: conformance requirements say this must be at least one character, thus just setting it to an empty string does not suffice. -- Geoffrey Sneddon <http://gsnedders.com/> Geoffrey Sneddon 2008-07-05T08:48:50 http://permalink.gmane.org/gmane.comp.python.lxml.devel/3826 Hi, Mark Seaborn wrote: It definitely was, likely over more than one release. Apparently, edgy has libxml2 2.6.26, so it should build and work. What is the problem you are experiencing? The respective code has been fixed and rewritten multiple times since 1.1 and IIRC the last corner cases were fixed as recent as somewhere in 2.0.x. In any case, don't use 1.3.1, as it's completely broken. I don't quite remember, that might be related to the fix or not. Stefan Stefan Behnel 2008-07-04T20:39:01 http://permalink.gmane.org/gmane.comp.python.lxml.devel/3825 Update: recompiled python-lxml-2.0.7-1.el5.x86_64.rpm with --without-threading, same problem. Thanks! John John Morris wrote: John Morris 2008-07-04T05:26:24 http://permalink.gmane.org/gmane.comp.python.lxml.devel/3824 Hi, John Morris wrote: http://codespeak.net/lxml/dev/element_classes.html Hope it doesn't hurt. Stefan Stefan Behnel 2008-07-03T19:17:05 http://permalink.gmane.org/gmane.comp.python.lxml.devel/3823 I'm trying to subclass lxml._Element. I'm completely new to python, so I'm definitely doing something wrong. The code below segfaults. Tried this with both lxml 1.3.6 and 2.0.7 (both from EPEL 5) along with libxslt 1.1.17 (CentOS 5 updates). Someone beat me over the head with a clue? Thanks! John Sysconf.py: -------------------- from lxml import etree class Sysconf(etree._Element): def __init__(self,datastore): etree._Element.__init__(self) test.py: -------------------- #!/usr/bin/python from lxml import etree import Sysconf sysconf = Sysconf.Sysconf("sysconf.xml") print etree.tostring(sysconf) John Morris 2008-07-03T19:07:41 http://permalink.gmane.org/gmane.comp.python.lxml.devel/3822 _______________________________________________ lxml-dev mailing list lxml-dev< at >codespeak.net http://codespeak.net/mailman/listinfo/lxml-dev jholg< at >gmx.de 2008-07-03T10:59:33 http://permalink.gmane.org/gmane.comp.python.lxml.devel/3821 Hi, Is it possible to parse slightly broken XML like this? etree.parse("""<xml sanitizer="true" sanitizer:value="true"/>""") >>> lxml.etree.XMLSyntaxError: Namespace prefix sanitizer for value on xml is not defined, line 1, column 31 Andrew Stromnov 2008-07-03T10:45:25 http://permalink.gmane.org/gmane.comp.python.lxml.devel/3820 _______________________________________________ lxml-dev mailing list lxml-dev< at >codespeak.net http://codespeak.net/mailman/listinfo/lxml-dev jholg< at >gmx.de 2008-07-03T05:56:34 http://permalink.gmane.org/gmane.comp.python.lxml.devel/3819 A quick blunder fix: The above works, but is not quite in accordance with the xml:id specification. Other XML processors may balk at the above. The error in this case is that the value of xml:id attributes cannot start with digits. The concept works, but it is a bad example. - Jim Washington Jim Washington 2008-07-02T17:24:07 http://permalink.gmane.org/gmane.comp.python.lxml.devel/3818 Hello 2008/7/2 Jim Washington <jwashin< at >vt.edu>: Indeed, converting the schema to a DTD solved my problem! Too simple to think of myself of course. Somehow the documentation must have confused me into believing validation with XMLSchema or DTD would work (I did understand RelaxNG wouldn't work). Converting the schema is simple using trang anyway (which I need to do in any case as I'm writing it in compact RelaxNG). That's quite nifty too! Don't think I'll use it this time but very good to know. Thanks for your tips Floris Floris Bruynooghe 2008-07-02T15:31:45 http://permalink.gmane.org/gmane.comp.python.lxml.devel/3817 [...] [...] [...] xml:id, http://www.w3.org/TR/xml-id/ works OK, if you do not want to use a schema. At least, it works with lxml 2.1.beta3. from lxml import etree XML_NAMESPACE='http://www.w3.org/XML/1998/namespace' XML_PREFIX= '{%s}' % XML_NAMESPACE f = etree.Element('test') f.set(XML_PREFIX+'id','23455') etree.tostring(f) '<test xml:id="23455"/>' g = etree.SubElement(f,'test1') g.set(XML_PREFIX+'id','23456') f.xpath('id("23456")') [<Element test1 at 777520>] f.xpath('id("23455")') [<Element test at 7774c8>] - Jim Washington Jim Washington 2008-07-02T14:17:12 http://permalink.gmane.org/gmane.comp.python.lxml.devel/3816 _______________________________________________ lxml-dev mailing list lxml-dev< at >codespeak.net http://codespeak.net/mailman/listinfo/lxml-dev jholg< at >gmx.de 2008-07-02T12:08:35 http://permalink.gmane.org/gmane.comp.python.lxml.devel/3815 Hi I've sent this to comp.lang.python a few days ago with no repsonse, so I hope you don't mind if I try here (if there is a better place please let me know)... Basically I'm trying to use the .xpath('id("foo")') method on an lxml tree but can't get it to work. Given the following XML: <root><child id="foo"/></root> And it's XMLSchema: <?xml version="1.0" encoding="UTF-8"?> <xs:schema xmlns:xs="http://www.w3.org/2001/XMLSchema" elementFormDefault="qualified"> <xs:element name="root"> <xs:complexType> <xs:sequence> <xs:element ref="child"/> </xs:sequence> </xs:complexType> </xs:element> <xs:element name="child"> <xs:complexType> <xs:attribute name="id" use="required" type="xs:ID"/> </xs:complexType> </xs:element> </xs:schema> Or in more readable, compact RelaxNG, form: element root { element child { attribute id { xsd:ID } } } Now I'm trying to parse the XML and use the .xpath() method to find the <child/> element using the id XPath functi Floris Bruynooghe 2008-07-02T09:34:49 http://permalink.gmane.org/gmane.comp.python.lxml.devel/3814 _______________________________________________ lxml-dev mailing list lxml-dev< at >codespeak.net http://codespeak.net/mailman/listinfo/lxml-dev jholg< at >gmx.de 2008-07-02T07:30:36 http://permalink.gmane.org/gmane.comp.python.lxml.devel/3813 _______________________________________________ lxml-dev mailing list lxml-dev< at >codespeak.net http://codespeak.net/mailman/listinfo/lxml-dev jholg< at >gmx.de 2008-07-02T07:27:16 http://permalink.gmane.org/gmane.comp.python.lxml.devel/3812 Hi, Eric Jahn wrote: I actually find it really helpful and I don't think many people have the problem you are experiencing. You didn't state what screen resolution or font size you are using, but it looks nice for me even in 1024x768. Maybe you can just try a different font? The web site is part of the source download, BTW, so you can also fix up doc/html/style.css yourself. Stefan Stefan Behnel 2008-07-02T06:11:33 http://permalink.gmane.org/gmane.comp.python.lxml.devel/3811 Hi, Eric Jahn wrote: Ah, now that you mention it, the above doesn't actually work. It only works for element text, not for attributes. I'll see if I can change that. Please do, any contribution is appreciated. Stefan Stefan Behnel 2008-07-01T17:19:36 http://permalink.gmane.org/gmane.comp.python.lxml.devel/3810 Hi Holger, jholg< at >gmx.de wrote: Glad to hear that. Thanks! Yep, please do so. Same as before. You get a byte string when you pass an encoding name, and a unicode string (str type) when you pass str. That's also something I like about the new interface. It would also require a bit more parameter checking and exception raising. The unicode option and the encoding are mutually exclusive, and unicode is not so far from an encoding that it would really merit an option on its own. Note also that you do not pass "Unicode" as a string but the unicode type, and you get a unicode object back. Stefan Stefan Behnel 2008-07-01T17:13:04 Search the mailing list at Gmane query http://search.gmane.org/?group=$group=gmane.comp.python.lxml.devel