Re: Python upgrade path (draft/proposal)

2001-10-20 Thread Chris Lawrence
On Oct 18, Matthias Klose wrote: > > > May I suggest a simpler alternative for (b) (or maybe an alternative "c"): > > > > Make package python-XXX containing support for both python 1.5 and > > python 2.1. For each python {1.5,2.1} that is installed, bytecompile > > the package's .py files on ins

Re: Python upgrade path (draft/proposal)

2001-10-18 Thread Matthias Klose
> May I suggest a simpler alternative for (b) (or maybe an alternative "c"): > > Make package python-XXX containing support for both python 1.5 and > python 2.1. For each python {1.5,2.1} that is installed, bytecompile > the package's .py files on install. Since we use > /usr/lib/pythonx.y/site

Re: Python upgrade path (draft/proposal)

2001-10-18 Thread Donovan Baarda
Quoting Matthias Klose <[EMAIL PROTECTED]>: > With the last python-1.5.2-18.2 NMU we have non-conflicting python1.5, > 2.0 and 2.1 packages in unstable, not more not less. > > Here two proposals, how to go further on. The first proposal is a > safer proposal (but needs more uploads and needs loon

Re: Python upgrade path (draft/proposal)

2001-10-17 Thread Anthony Towns
On Wed, Oct 17, 2001 at 11:06:37PM +0200, Matthias Klose wrote: > 4) Packages not compatible with python2 need to be uploaded >to use the python1.5 packages/binary. NMU's should be allowed >to fix these ... Possibly, you should reupload them renamed to be "python1.5-foo", as well, so that

Re: Python upgrade path (draft/proposal)

2001-10-17 Thread Chris Lawrence
On Oct 17, Matthias Klose wrote: > With the last python-1.5.2-18.2 NMU we have non-conflicting python1.5, > 2.0 and 2.1 packages in unstable, not more not less. > > Here two proposals, how to go further on. The first proposal is a > safer proposal (but needs more uploads and needs loong). The seco