From: Arfrever Frehtes Taifersar Arahesis <Arfrever@gentoo.org>
To: Gentoo Development <gentoo-dev@lists.gentoo.org>
Subject: Re: [gentoo-dev] PyXML
Date: Tue, 17 May 2011 21:12:00 +0200 [thread overview]
Message-ID: <201105172112.01100.Arfrever@gentoo.org> (raw)
In-Reply-To: <4DD2C1D1.1060107@gentoo.org>
[-- Attachment #1: Type: Text/Plain, Size: 2208 bytes --]
2011-05-17 20:43:29 Tomáš Chvátal napisał(a):
> 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.
I had already explained it in many places.
> 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?
Fixes for at least the following bugs are absent when PyXML is installed:
http://bugs.python.org/issue4877
http://bugs.python.org/issue6098
http://bugs.python.org/issue5762
http://bugs.python.org/issue5027
http://bugs.python.org/issue9054
http://bugs.python.org/issue777884
http://bugs.python.org/issue1433694
http://bugs.python.org/issue847665
http://bugs.python.org/issue1472827
http://bugs.python.org/issue1094164
http://bugs.python.org/issue1309009
http://bugs.python.org/issue1262320
http://bugs.python.org/issue925152
--
Arfrever Frehtes Taifersar Arahesis
[-- Attachment #2: This is a digitally signed message part. --]
[-- Type: application/pgp-signature, Size: 836 bytes --]
next prev parent reply other threads:[~2011-05-17 19:13 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-05-10 21:21 [gentoo-dev] PyXML Arfrever Frehtes Taifersar Arahesis
2011-05-11 10:30 ` Tomáš Chvátal
2011-05-11 17:53 ` Arfrever Frehtes Taifersar Arahesis
2011-05-17 17:11 ` Mark Loeser
2011-05-17 17:32 ` Markos Chandras
2011-05-17 18:19 ` Arfrever Frehtes Taifersar Arahesis
2011-05-17 18:24 ` Mark Loeser
2011-05-17 18:33 ` Arfrever Frehtes Taifersar Arahesis
2011-05-17 18:29 ` Arfrever Frehtes Taifersar Arahesis
2011-05-17 18:43 ` Tomáš Chvátal
2011-05-17 19:12 ` Arfrever Frehtes Taifersar Arahesis [this message]
2011-05-17 19:21 ` Tomáš Chvátal
2011-05-17 20:53 ` Arfrever Frehtes Taifersar Arahesis
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=201105172112.01100.Arfrever@gentoo.org \
--to=arfrever@gentoo.org \
--cc=gentoo-dev@lists.gentoo.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox