Mailman 3 December 2014 - lxml - The Python XML Toolkit

Help me on installation please ...
by Adarsh LR Dec. 16, 2014

Dec. 16, 2014

Namaskar ... I am from india, Anyone who can help me with a quick installer of pip.. I am not even able to install this python script Anyways ... even I am working on this Lets go Adarsh L Raju

1 0

Trouble running code on Windows Server 2012
by Ken Norris Dec. 16, 2014

Dec. 16, 2014

Hi, I'm having trouble running a code I wrote that uses lxml in python on a Windows 2012 Server. I originally wrote the script on MacOSx and it works well. I tried to run the same on the server. The code runs without error and it produces PDFs, however when I try to open them up they are corrupted or show up as blank. I followed some steps (i.e. following the instructions in the documentation to install the dependencies of lxml and by reseting the PATH env to make sure the dependencies were routing to the proper place) to no avail. I'll attach the script. I'm doing research in the economics department at UBC in Vancouver, Canada. My coding skills are coming along but they're far from perfect. Any help you could provide would be great. Thanks, Ken

2 1

Re: [lxml] Support default_namespace parameter in write method?
by Stefan Behnel Dec. 13, 2014

Dec. 13, 2014

Charlie Clark schrieb am 07.12.2014 um 12:00: > Am .12.2014, 10:05 Uhr, schrieb Stefan Behnel: >> Not sure. It's due to an inherent difference in the tree models of libxml2 >> and ElementTree: the latter does not know about prefixes at all and handles >> them only in the serialiser, whereas libxml2 takes them from the in-memory >> tree. There is no override in libxml2's serialiser, so it would require >> modifying the tree's namespaces during serialisation (i.e. modification >> during a supposed read-only operation). I guess it's worth trying out, >> though. > > I thought there might be something like that. But would it be possible to > allow the registration of an empty namespace (as ElementTree allows)? > Currently this is only possible with nsmap. BTW. what are the constraints > on nsmap? The attribute is not writable but __setitem__ does not raise an > exception. Yes, it's actually documented (see docstring) that changing an Element's nsmap has no effect. The property returns a real dict that contains all prefix-namespace mappings known in the context of this Element in the tree. But it has no actual connection to that Element that could pass back modifications. I think the problem is that it was never obvious to me what the semantics should be here. It feels wrong if modifying a mapping that includes all ancestor namespaces changes the namespaces defined on a specific node. And would it then update the subtree of that Element? Then reading the property would give you access to the ancestor state and modifying it would change the children? Strange. If you change the namespace of a prefix, would it then have to go back to the ancestor that defined the modified prefix and changing its entire subtree? That sounds even worse. And what would happen if you deleted a prefix that's in use? I agree that the feature of modifying the namespace mapping is missing, though. If someone has a good idea how this should work, I'm all eyes. > register_namespace("", "http://example.com/whatever") # works in > ElementTree but not in lxml Ah, yes. Not sure the error you get was intended. It would be easy to make this work, but then, register_namespace() changes global library state. Globally setting up a prefix-namespace mapping is not a great idea already (it's ok as long as the prefix is a generally accepted de-facto standard), but setting a global default namespace seems like asking for trouble and interference with other code. The mapping is bidirectional and if multiple default namespace mappings are registered, one will overwrite the other and the result will depend on who happens to be last. Rearrange some imports and loose your pretty output? If you're lucky, you'll at least see some of your tests fail, but I guess prefixes are rarely tested for. Stefan

1 0

using Xpath to look for one or another element
by Martin Mueller Dec. 11, 2014

Dec. 11, 2014

I know how to use finditer to select one type of element, as in speech.iterfind('.//tei:w', namespaces = {'tei':'http://www.tei-c.org/ns/1.0'}) which selects all the <w> descendants of the parent element. But what if I want to find <w> OR <c> elements. As I understand from a posting in stackoverflow, iterfind('.//tei:w |.//tei:c',namespaces = {'tei':'http://www.tei-c.org/ns/1.0'}) should do the trick in regular expression mode. But it doesn't seem to work. Am I doing something wrong or have I hit a limit of the program?

2 1

Support default_namespace parameter in write method?
by Charlie Clark Dec. 5, 2014

Dec. 5, 2014

Hiya, since Python 2.7 the xml.etree's ElementTree has supported a default namespace when serialising XML: write(file, encoding="us-ascii", xml_declaration=None, default_namespace=None, method="xml") Would it be possible to support the signature in lxml? This would make coding for both libraries easier where a default namespace is desired, as in certain parts of openpyxl, due to overly fussy or downright buggy clients? 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

2 1

tests failing due to encoding errors on non-utf-8 system
by Holger Joukl Dec. 5, 2014

Dec. 5, 2014

Hi, I just encountered failing lxml tests on a system with non-UTF-8 locale: (don't get irritated by the overall test case count, I've disabled some tests) ... 1626/1626 (100.0%): txt (xpathxslt) Doctest: xpathxslt.txt ====================================================================== ERROR: test_etree_parse_io_error (lxml.tests.test_io.ETreeIOTestCase) ---------------------------------------------------------------------- Traceback (most recent call last): File "/apps/prod/releases/2.0/lib/python2.7/unittest/case.py", line 331, in run testMethod() File "/var/tmp/hjoukl/BUILD/NEW/64bit/gcc/2014-QX/lxml-3.4.1/src/lxml/tests/test_io.py", line 276, in test_etree_parse_io_error dn = tempfile.mkdtemp(prefix=dirnameRU) File "/apps/prod/releases/2.0/lib/python2.7/tempfile.py", line 329, in mkdtemp _os.mkdir(file, 0700) UnicodeEncodeError: 'latin-1' codec can't encode character u'\u0161' in position 6: ordinal not in range(256) ====================================================================== ERROR: test_etree_parse_io_error (lxml.tests.test_io.ElementTreeIOTestCase) ---------------------------------------------------------------------- Traceback (most recent call last): File "/apps/prod/releases/2.0/lib/python2.7/unittest/case.py", line 331, in run testMethod() File "/var/tmp/hjoukl/BUILD/NEW/64bit/gcc/2014-QX/lxml-3.4.1/src/lxml/tests/test_io.py", line 276, in test_etree_parse_io_error dn = tempfile.mkdtemp(prefix=dirnameRU) File "/apps/prod/releases/2.0/lib/python2.7/tempfile.py", line 329, in mkdtemp _os.mkdir(file, 0700) UnicodeEncodeError: 'latin-1' codec can't encode character u'\u0161' in position 6: ordinal not in range(256) ---------------------------------------------------------------------- Ran 1626 tests in 56.208s FAILED (errors=2) Skipping tests in lxml.cssselect - external cssselect package is not installed Comparing with ElementTree 1.3.0 TESTED VERSION: 3.4.1 Python: sys.version_info(major=2, minor=7, micro=5, releaselevel='final', serial=0) lxml.etree: (3, 4, 1, 0) libxml used: (2, 9, 1) libxml compiled: (2, 9, 1) libxslt used: (1, 1, 28) libxslt compiled: (1, 1, 28) make: *** [test_inplace] Error 1 This is caused by the directory path characters of a temp directory that are not representable in the system's encoding: def test_etree_parse_io_error(self): # this is a directory name that contains characters beyond latin-1 dirnameEN = _str('Directory') dirnameRU = _str('Ã~PÅ¡Ã~PÂ°Ã~Qâ~@~ZÃ~PÂ°Ã~PÂ»Ã~PÂŸÃ~PÂ³') filename = _str('nosuchfile.xml') dn = tempfile.mkdtemp(prefix=dirnameEN) try: self.assertRaises(IOError, self.etree.parse, os.path.join(dn, filename)) finally: os.rmdir(dn) dn = tempfile.mkdtemp(prefix=dirnameRU) try: self.assertRaises(IOError, self.etree.parse, os.path.join(dn, filename)) finally: os.rmdir(dn) I'm unsure of what a proper fix for this should look like. Refactor to 2 separate tests and disable the non-ascii dir path test based on sys.getfilesystemencoding ()? Or rather do dn = tempfile.mkdtemp(prefix=dirnameRU.encode('utf-8')) ? Holger Landesbank Baden-Wuerttemberg Anstalt des oeffentlichen Rechts Hauptsitze: Stuttgart, Karlsruhe, Mannheim, Mainz HRA 12704 Amtsgericht Stuttgart

2 1