-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Dne 10.5.2011 23:21, Arfrever Frehtes Taifersar Arahesis napsal(a): > PyXML is dead: > http://mail.python.org/pipermail/xml-sig/2004-November/010735.html > http://mail.python.org/pipermail/xml-sig/2006-June/011545.html > > PyXML provides _xmlplus module, which replaces xml module (from standard > library) at run time, > which might result in various problems. > > I'm planning to implement the following solution: > - Python >=2.7.1-r2:2.7 will provide xml.use_pyxml() function. Calling of > this function will be > necessary to use replace xml module with _xmlplus module. Python > >=2.7.1-r2:2.7 will be added > to the tree in next week and will be temporarily package.masked. Later this > change will be > backported to new versions in older slots. > - All packages, which use PyXML, will have to be patched to call > xml.use_pyxml(). The following > code should be added before first import of anything from xml module: > > import xml > if hasattr(xml, "use_pyxml"): > xml.use_pyxml() > > This code works with previous versions of Python, so no changes in > dependencies are needed. > As I already asked, what problem do we have to keep PyXML in main tree to be used with python2.
Your specific hack introduce different behaviour for python2.7.1-r2 where you do not explain the need for it at all. It is just python2 thing and we can happily use PyXML as it works even with latest python-2.7. So where is the problem? Failing python tests? Then patch PyXML itself to use it properly, but keep it as is. When app migrate to py3 they will have to loose the PyXML dependency anyway. -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.17 (GNU/Linux) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/ iEYEARECAAYFAk3SwdEACgkQHB6c3gNBRYenyACeOMsOpUJwgPLBeyAZtcHeVVAH j7sAn0B8f8/UINM4xVsws9xDsURrnYGj =H8Jw -----END PGP SIGNATURE-----
