Re: Python 2.6

2010-01-03 Thread Stefano Zacchiroli
On Sun, Jan 03, 2010 at 08:01:10PM +0100, Bastian Venthur wrote: > I'm sorry to bring this topic up again, but what is the status of Python > 2.6 and Squeeze? I wrote a mail to doko on 2009-12-13 asking him what > his plans are and if he needs help but didn't receive an answer yet. Has > anyone mor

Re: Python 2.6

2010-01-03 Thread Luk Claes
Bastian Venthur wrote: > Hi all, > > I'm sorry to bring this topic up again, but what is the status of Python > 2.6 and Squeeze? I wrote a mail to doko on 2009-12-13 asking him what > his plans are and if he needs help but didn't receive an answer yet. Has > anyone more information? python 2.6 wi

Re: Python 2.6? A Python transition?

2009-08-30 Thread Josselin Mouette
Le jeudi 27 août 2009 à 19:05 -0700, Russ Allbery a écrit : > > * fixing paths from site-packages to *-packages (since the path > > now depends on the Python version, yay) > > I may be confused by this, but so far as I can tell, I don't have to do > anything for this to work for the

Re: Python 2.6? A Python transition?

2009-08-28 Thread Luca Falavigna
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Russ Allbery ha scritto: >> First, the installation path changed from site-packages to >> dist-packages. This means that most Python packages will need two >> changes: > >> * passing --install-layout=deb to setup.py > > Okay, that's easy enoug

Re: Python 2.6? A Python transition?

2009-08-27 Thread Mark Felder
I have a program that depends on 2.6 but I can't seem to get the required modules to install in squeeze/sid. The ones in the package management system only work for 2.5. Is there some big transition coming? Mark On Aug 27, 2009, at 21:05, Russ Allbery wrote: Josselin Mouette writes:

Re: Python 2.6? A Python transition?

2009-08-27 Thread Russ Allbery
Josselin Mouette writes: > First, the installation path changed from site-packages to > dist-packages. This means that most Python packages will need two > changes: > * passing --install-layout=deb to setup.py Okay, that's easy enough. I assume that doesn't break builds for Python 2.5 (

Re: Python 2.6? A Python transition?

2009-08-26 Thread Bernd Zeimetz
Michal Čihař wrote: > Hi > > Dne Wed, 26 Aug 2009 11:00:40 +0200 > Josselin Mouette napsal(a): > >> To put it simply: >> * Most packages using cdbs should be safe. >> * Some packages using dh (most of those building only one binary >> package) should be safe. >> * Al

Re: Python 2.6? A Python transition?

2009-08-26 Thread Michal Čihař
Hi Dne Wed, 26 Aug 2009 11:00:40 +0200 Josselin Mouette napsal(a): > To put it simply: > * Most packages using cdbs should be safe. > * Some packages using dh (most of those building only one binary > package) should be safe. > * All the rest needs updating, at least

Re: Python 2.6? A Python transition?

2009-08-26 Thread Luca Falavigna
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Russ Allbery ha scritto: > Is there a best practice guide somewhere, and if we are doing a > transition, a guide for those of us who only have ancillary involvement in > Python packaging telling us what to do? Some references can be found here (and in

Re: Python 2.6? A Python transition?

2009-08-26 Thread Bernd Zeimetz
Josselin Mouette wrote: > There are two problems with adding Python 2.6 to the supported versions. > > First, the installation path changed from site-packages to > dist-packages. This means that most Python packages will need two > changes: > * passing --install-layout=deb to setup.py >

Re: Python 2.6? A Python transition?

2009-08-26 Thread Josselin Mouette
Le mardi 25 août 2009 à 10:10 -0700, Russ Allbery a écrit : > I have a few packages that build either Python modules or that embed > Python. I see that for the one that builds Python modules (remctl), > Ubuntu has patched it for a Python 2.6 transition using new makefile > machinery that I don't