[opensuse-factory] python-elementtree in Factory
I've noticed that python-elementtree was removed in Factory. Will it be returning? It's a very popular module that's used in a lot of Python projects, including osc. -- James Oakley jfunk@funktronics.ca --------------------------------------------------------------------- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-factory+help@opensuse.org
On Fri, Feb 23, 2007 at 02:22:27PM -0400, James Oakley wrote:
I've noticed that python-elementtree was removed in Factory. Will it be returning?
No, most likely it won't.
It's a very popular module that's used in a lot of Python projects, including osc.
osc already has code in place to use Python 2.5's xml.etree. (We just need to drop the python-elementtree requirement for $dist >= 10.2). All other packages that depended on python-elementtree should have been patched to use xml.etree. If there are still hidden problems with this, let me know! Is there any functionally that existed in python-elementtree, which is not part of xml.etree that you relied on? (I only know of SimpleXMLWriter, which was only used by repoview and therefore is now being shipped with repoview.) 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
On Friday 23 February 2007 5:07 pm, Christoph Thiel wrote:
On Fri, Feb 23, 2007 at 02:22:27PM -0400, James Oakley wrote:
I've noticed that python-elementtree was removed in Factory. Will it be returning?
No, most likely it won't.
It's a very popular module that's used in a lot of Python projects, including osc.
osc already has code in place to use Python 2.5's xml.etree. (We just need to drop the python-elementtree requirement for $dist >= 10.2). All other packages that depended on python-elementtree should have been patched to use xml.etree. If there are still hidden problems with this, let me know!
Is there any functionally that existed in python-elementtree, which is not part of xml.etree that you relied on? (I only know of SimpleXMLWriter, which was only used by repoview and therefore is now being shipped with repoview.)
A list of differences can be found at http://codespeak.net/lxml/compatibility.html I have no problem porting my code, but other people may have trouble. Why not make ElementTree raise a DeprecationWarning for a short period to give people a chance to catch up? -- James Oakley jfunk@funktronics.ca --------------------------------------------------------------------- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-factory+help@opensuse.org
On Mon, Feb 26, 2007 at 10:39:59AM -0400, James Oakley wrote:
osc already has code in place to use Python 2.5's xml.etree. (We just need to drop the python-elementtree requirement for $dist >= 10.2). All other packages that depended on python-elementtree should have been patched to use xml.etree. If there are still hidden problems with this, let me know!
Is there any functionally that existed in python-elementtree, which is not part of xml.etree that you relied on? (I only know of SimpleXMLWriter, which was only used by repoview and therefore is now being shipped with repoview.)
A list of differences can be found at http://codespeak.net/lxml/compatibility.html
Are you sure this is really the in-tree Python 2.5 etree.xml? It looks like a different thing to me -- at first glace.
I have no problem porting my code, but other people may have trouble. Why not make ElementTree raise a DeprecationWarning for a short period to give people a chance to catch up?
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. 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
On Monday 26 February 2007 11:12 am, Christoph Thiel wrote:
A list of differences can be found at http://codespeak.net/lxml/compatibility.html
Are you sure this is really the in-tree Python 2.5 etree.xml? It looks like a different thing to me -- at first glace.
Ah, you're right. lxml.etree is an ElementTree implementation under lxml, and xml.etree is a subset of Fredrik Lundh's module.
I have no problem porting my code, but other people may have trouble. Why not make ElementTree raise a DeprecationWarning for a short period to give people a chance to catch up?
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. -- James Oakley jfunk@funktronics.ca --------------------------------------------------------------------- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-factory+help@opensuse.org
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
On Monday 26 February 2007 4:21 pm, Christoph Thiel wrote:
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.
That's cool. I'll send patches downstream to the projects using my code. Thanks, -- James Oakley jfunk@funktronics.ca --------------------------------------------------------------------- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-factory+help@opensuse.org
participants (2)
-
Christoph Thiel -
James Oakley