Report on the situation of python2.5 in Debian

[Bernd Zeimetz]

Josselin Mouette wrote:
> Le vendredi 05 octobre 2007 à 20:42 +0200, Bernd Zeimetz a écrit :
>> You have missed Zope.
>> It is not possible to run Zope 2.X with Python 2.5 yet, same for Zope 3.
>> The problems in there are nothing a maintainer could fix, except
>> somebody is willing to pay several days (weeks!?) of work.
>> Changing the default python version also means to go trough all Zope
>> packages and replace /usr/bin/python by /usr/bin/python2.4.
> 
> My guess is that must have already been done, because all zope packages
> (except those I have listed) already depend on python2.4.

They depend on python2.4, but I'm pretty sure a lot of them use
#!/usr/bin/python, unfortunately. I'm forwading the mail to the Zope
lsit therefore.



>> Does the list include those packages which are not conform to the new
>> Python policy? There're still several of them out there. A zero-day NMU
>> policy would be good to have here, too.
>> http://bugs.debian.org/from:madcoder-python-transition@debian.org;pend-exc=done;exclude=fixed
> 
> AFAICT the remaining packages shouldn't prevent python2.5 to migrate to
> testing. Still, these bugs also deserve a 0-day NMU policy indeed.

As far as I remember several of them were supposed to be orphaned
anyway, removing instead of fixing would be the way for them.


>>>         mod-wsgi
>> It's not possible to use more than one python version with mod-wsgi,
>> therefore it will only work and be build against the default python
>> version. A binNMU after changing the version should work well.
> 
> I think it should be possible, by building several versions and using a
> rtupdate hook to change a symbolic link pointing to one of them.

Probably I'll implement that, and provide a module for every python
version. That's something I have to talk trough with upstream first, though.



-- 
Bernd Zeimetz
<bernd at bzed.de>                         <http://bzed.de/>