It is the same library (same API, same features) but ElementTree is implemented in Python and cElementTree is implemented in C. If you can, use the C implementation because it is optimized for fast parsing and low memory use, and is 15-20 times faster than the Python implementation. Use the Python version if you are … Read more
The easiest solution is probably using lxml, where you can set a parser option to ignore white space between elements: >>> from lxml import etree >>> parser = etree.XMLParser(remove_blank_text=True) >>> xml_str=””‘<root> >>> <head></head> >>> <content></content> >>> </root>”’ >>> elem = etree.XML(xml_str, parser=parser) >>> print etree.tostring(elem) <root><head/><content/></root> This will probably be enough for your needs, but … Read more
JSON is more compact and can be easily loaded in JavaScript. XML is stricter and has support for schemas and namespaces. On the face of it JSON seems superior in every way – it’s flexible, more compact and in many cases easier to use (especially when working with JavaScript), however it lacks some key features, … Read more
General case The markup in the document following the root element must be well-formed. This error indicates that your XML has markup following the root element. In order to be well-formed, XML must have exactly one root element, and there can be no further markup following the single root element. One root element example (GOOD) … Read more
When I go to the beautifulsoup 4.0 documentation, the first page has this information: (The BeautifulSoup package is probably not what you want. That’s the previous major release, Beautiful Soup 3. Lots of software uses BS3, so it’s still available, but if you’re writing new code you should install beautifulsoup4.)
I eventually figured out there was a byte mark exception and removed it using this code: string _byteOrderMarkUtf8 = Encoding.UTF8.GetString(Encoding.UTF8.GetPreamble()); if (xml.StartsWith(_byteOrderMarkUtf8)) { var lastIndexOfUtf8 = _byteOrderMarkUtf8.Length-1; xml = xml.Remove(0, lastIndexOfUtf8); }
Here’s a slightly shorter solution. Maximum: /foo/bar/@score[not(. < ../../bar/@score)][1] Minimum: /foo/bar/@score[not(. > ../../bar/@score)][1] I’ve edited the predicate so that it’s applicable to any sequence of bar, even if you decide to change the path. Note that parent of attribute is the element to which it belongs. If embedding these queries in XML files like XSLT … Read more
I want to comment that the script in current accepted answer doesn’t validate errors about incorrect orders of elements of xs:sequence. For example: test.xml <addresses xmlns:xsi=”http://www.w3.org/2001/XMLSchema-instance” xsi:noNamespaceSchemaLocation=’test.xsd’> <address> <street>Baker street 5</street> <name>Joe Tester</name> </address> </addresses> test.xsd <xs:schema xmlns:xs=”http://www.w3.org/2001/XMLSchema”> <xs:element name=”addresses”> <xs:complexType> <xs:sequence> <xs:element ref=”address” minOccurs=”1″ maxOccurs=”unbounded”/> </xs:sequence> </xs:complexType> </xs:element> <xs:element name=”address”> <xs:complexType> <xs:sequence> <xs:element ref=”name” … Read more