At some point, Gregor Hoffleit <[EMAIL PROTECTED]> wrote: > My proposal for woody: Python 1.5.2 is renamed to python1.5-*. Python > 2.1.1 will be shipped as python2.1-*. Do we need python2.0-* as well ?
I don't see why. Looking at the list of changes from 2.0 to 2.1 at http://www.amk.ca/python/2.1/ I can see only a few difficulties in using code written for 2.0 in 2.1: - complex numbers can only be compared with == and != now - 'from module import *' will only import some of the names in module if module has an __all__ attribute There are some C API changes too, but the old API is still there. None of these look like they'll break old code (or require more than 5 minutes to fix). > Then, we still have to agree on a strategy how to set up the > dependencies, in order to make the upgrade work in an intuitive way. > > For maintainers of Python extension modules, this would mean that they > would have to build one package for each included Python version, e.g. > python1.5-mysqldb, python2.0-mysqldb and python2.1-mysqldb. > > There would be no python-* packages in woody!!! How about a 'python' package, much like the 'gcc' package, whose only purpose is to set what is the default python interpreter for Debian? It would depend on python2.1-base. -- |>|\/|< /--------------------------------------------------------------------------\ |David M. Cooke |[EMAIL PROTECTED]
