On Tue, Dec 18, 2007 at 11:03:16PM +0900, js wrote: > Hi, > > Today I read Debian Python Policy and found that it says that > "At any given time, the package python will represent the current > default Debian Python version. > The default Debian Python version should alway be the latest stable > upstream release that can be integrated in the distribution. " > > Unfortunately, this is not true, at least for today's "etch", the > stable debian release. > I know etch has python2.5 package as well as 2.4, > but because 2.4 is treated as default python on etch, > installing python-related packages is more than aptitude install python-*. > > I'm sure that you python guys are already working on this, > but let me ask you some of my questions. > > - What problem prevents python2.5 from becoming "default"? > - Is there any estimated date that python2.5 will get "default"? > - Is there anything I can do to get your work done quickly? > Well, at the time that Etch was released, there were probably a number of important packages that did not support python 2.5 or did not work with it on some way or even at all.
Since Etch is already released, this will not change for Etch. The earliest opportunity to fix this would be the release of Lenny. Regards, -Roberto -- Roberto C. Sánchez http://people.connexer.com/~roberto http://www.connexer.com
signature.asc
Description: Digital signature
