Python 2.6 transition update

External Since: Nov 23, 2008 Posts: 16

Dear Debian Python,

As you may be aware, I have been making quite a bit of hue and cry
about the Python 2.6 transition blocking bugs[1]. I have managed to
submit patches for most of the packages to _make them build_ with
Python 2.6. However, as Paul Wise righly points out[2], my patches
merely make the packages build; I haven't really tested any of these
packages with Python 2.6 (In fact, I observe that fonttools is
dependent on python-numpy, which is not yet built with python 2.6, so
I shouldn't have sent that patch at all!). So, in my opinion, it would
be best if the maintainer, or someone who can invest time into
verifying that these packages do work with Python 2.6, performs
uploads to fix the blocking bugs.

Thanks!

Kumar

[1]: http://bugs.debian.org/cgi-bin/pkgreport.cgi?users=debian-python@lists...bian.or
[2]: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=547821#20
--
Kumar Appaiah

--
To UNSUBSCRIBE, email to debian-python-REQUEST RemoveThis @lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmaster RemoveThis @lists.debian.org

External Since: Nov 22, 2006 Posts: 80

Wow... no replies in this imho important thread...

Hi Kumar,

Thanks for starting the roll. Imho numpy/scipy and then any other
python- with binary modules and not absent rdepends should be indeed
rebuilt with 2.6 and installed in the (ch)root to verify if any other
2.6 package dependent on them not only builds but at least imports.

Module name should be easy to figure out in many cases - for most of
them since due to policy's "should" iirc rule module name should be
actual suffix of the "python-" package name. If it does imports fine I
would look for module.test and if present -- run it. That would imho be
very valuable information for package maintainers... it might even be
worth to setup some temporary repository with builds of the packages
with binary extensions (e.g numpy) for 2.6 so that anyone willing to
troubleshoot his dependent package for 2.6 compatibility could use
prebuilt packages from there instead of manual redoing what you
are doing Wink

Cheers,
Yarik

On Wed, 14 Oct 2009, Kumar Appaiah wrote:

> Dear Debian Python,

> As you may be aware, I have been making quite a bit of hue and cry
> about the Python 2.6 transition blocking bugs[1]. I have managed to
> submit patches for most of the packages to _make them build_ with
> Python 2.6. However, as Paul Wise righly points out[2], my patches
> merely make the packages build; I haven't really tested any of these
> packages with Python 2.6 (In fact, I observe that fonttools is
> dependent on python-numpy, which is not yet built with python 2.6, so
> I shouldn't have sent that patch at all!). So, in my opinion, it would
> be best if the maintainer, or someone who can invest time into
> verifying that these packages do work with Python 2.6, performs
> uploads to fix the blocking bugs.

> Thanks!

> Kumar

> [1]: http://bugs.debian.org/cgi-bin/pkgreport.cgi?users=debian-python@lists...bian.or
> [2]: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=547821#20
--
.-.
=------------------------------ /v\ ----------------------------=
Keep in touch // \\ (yoh@|www.)onerussian.com
Yaroslav Halchenko /( )\ ICQ#: 60653192
Linux User ^^-^^ [175555]

--
To UNSUBSCRIBE, email to debian-python-REQUEST RemoveThis @lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmaster RemoveThis @lists.debian.org