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 loong).
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
[Please CC me on replies]
I made a new version of the Debian Python Policy, based on Neil's
Python Policy (0.1), the new Python packages in unstable and Donovan's
comments on the upgrade procedure.
It's appended and available from http://ftp-master.debian.org/~doko/
(including the sgml source).
Matthias Klose wrote:
At any given time, the package `python-base' should represent the
current stable upstream version of Python. XXX: Should we have an
exception for the case, when a new upstream version is released during
a Debian freeze?
It should probably be reworded
4 matches
Mail list logo
