Donovan Baarda <[EMAIL PROTECTED]> writes: [...]
> IMHO, the best solution given what you have described above is to make each > new release of python as a "python-X.Y" package that installs > "/usr/bin/pythonX.Y", and have another small "python" package which depends > on the latest "python-X.Y" and installs a "/usr/bin/python" link to > "/usr/bin/pythonX.Y". [...] > I'm sorry for bringing this all up now, when it sounds like the policy and > packages are basicly done... I was late into this and thought I'd throw in > my 2c. You said that very well. Pretty much exactly what I have been thinking. Better late than never, but at the end of the day I suppose the maintainer, of python (and perhaps all the packages which depend on it, should decide, because they are doing the work, and I'm, not!