On Tue, May 17, 2011 at 01:11:57PM -0400, Mark Loeser wrote:
> Arfrever Frehtes Taifersar Arahesis <Arfrever@gentoo.org> said:
> > 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()
> 
> Is this "use_pyxml" upstream?  From what you are saying, it is not. In
> that case, we have just made patches for every package that will never
> be allowed upstream.  Why not do something more worthwhile than waste the
> time of having to support something that might just become a problem to
> maintain in the future?
> 
> -- 
> Mark Loeser
> email         -   halcy0n AT gentoo DOT org
> email         -   mark AT halcy0n DOT com
> web           -   http://www.halcy0n.com

I second that. Why do we need to make all the work fixing packages
instead of letting upstream do their job? I am not so excited to 
fix every package I maintain as it is quite possible to introduce
regressions in the process. Furthermore, I don't understand your first
message. You say that you will provide xml.use_pyxml() function on
python-2.7. Is this code official or you are just patching the official
python releases?
Anyway, as I said, I'd rather wait for upstream to fix their packages
instead of me.

Regards,
-- 
Markos Chandras / Gentoo Linux Developer / Key ID: B4AFF2C2