Re: Debian Python policy.
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!
Re: Question for the transition
Neil Schemenauer [EMAIL PROTECTED] writes: Jim Penny wrote: This is not all that simple. python2.1 conflicts with zope2.3.x and python1.5 conflicts with zope2.4.x. In that case I think it's better to create python1.5 and zope2.3 legacy packages for people who can't upgrade. I prefer this approach. A legacy package which a few people will have installed for a period of transition. Everyone else uses the latest version of python-base. If something breaks (like zope) then you reinstall the old package and report a bug. The zope maintainer can then add a dependancy like requires python = 1.5
Python 2.1
I've read through archives on this in the past, feel free to suggest other URL's if this is a discussed to death topic, but; Python 2.1 in now GPL compatable right? I saw some 2.1 packages in one of the debian developers home directories. They aren't release though, and that can be a little annoying if you want to compile modules etc, and there are dependacy issues. What's the story for python2 in Debian? Also has it been decided that we will need python 1.5 for the foreseable future? I just like to hack with python, but I like to feel I'm using the latest software. Debian has traditionally been very good for that, because apt-get made it so. However in relation to python, it doesn't seem to be a safe assumption.
