Both having just a python package for the default python version and having versioned python packages have problems with the upgrade path from potato. How about a system where we do things like gcc does by providing a python package that depends on the default version of python and have /usr/bin/python managed by alternatives? If the default python for woody would still be python1.5 (also python1.5 should have the highest priority so that even if the user installs python2.1 or whatever things would still work) all the upgrade problems would be solved. This way we could gradually move to a system where modules that install stuff in /usr/lib/python*/site-packages would depend on the versioned package and not the python package. Also this way simple scripts that just need /usr/bin/python would work by just depending on python and users could use whatever python version they see fit.
-- Arto Jantunen
