On Mon, Feb 26, 2007 at 04:01:39PM -0400, James Oakley wrote:
I guess we can add the package back, in case it really turns out to be a problem. But as of today I'm not aware of any.
According to this, xml.etree is a subset of the full distribution:
http://docs.python.org/whatsnew/modules.html#SECTION0001420000000000000000
For myself, this is not really a problem, since I can update my code and I only use core features. However, there are plenty of programs that use ElementTree directly that are not supplied in OpenSUSE. I know of a couple of programs that are using local forks of some of my code using ElementTree.
The way I see it, most projects actually ship their own in-tree copy of ElementTree (e.g. smart does). So, most of the stuff should be alright -- or needs to be "ported" to 2.5's xml.etree anyways. So, for now, I'd suggest we stick with the current sitation -- without python-elementtree. If it turns out, there is actual demand for it, we will have to reconsider. In either case, many thanks for bringing this up! Best, Christoph -- Christoph Thiel, Tech. Project Management, Research & Development SUSE LINUX Products GmbH, GF: Markus Rex, HRB 16746 (AG Nürnberg) --------------------------------------------------------------------- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-factory+help@opensuse.org