On Fri, Nov 10, 2006, Alexandre Fayolle wrote: > > Concerning python2.5, it's not enabled yet because it's not expected to > > be the default version in etch, but I suppose it could be now that it > > is officially released and in sync in etch. > In my opinion, shipping etch with python2.5 (even as non default) and no > extension module compiled for python2.5 is a bit strange.
Well, I can only agree. My sentence wasn't very clear in that I meant that "I suppose it could be [enabled] now", and not be the default. > > > Any package building C extension modules rebuilt with the current setup > > > will only compile the C extension for python2.4, which is not what we > > > want. > > I think it is. :) > I'd like real python2.5 support in etch... I was commenting on the python2.3 support which is being dropped. Yeah, 2.5 for etch would certainly be nice. > /me goes to reupload python-psyco without python2.3 support. Hmm, I'm not sure it's a good idea to override an archive wide behavior on a per package basis. :-/ -- Loïc Minier <[EMAIL PROTECTED]>
