Donovan Baarda writes: > On Sun, Oct 21, 2001 at 10:27:54AM +1300, Carey Evans wrote: > > Matthias Klose <[EMAIL PROTECTED]> writes: > > > > [...] > > > > > exactly. But you see that these packages will break when you try to > > > upgrade. We can't make 2.1 the default right now, because we will > > > _silently_ break packages. Before python can point to python2.1, we > > > will have to fix all packages which depend on python-base, to depend > > > on python-base (<< 1.6). > > > > But if we get Python 2.1 into Debian 3.0, people will be upgrading > > from the old Python 1.5 packages in Debian 2.2 directly to the new > > packages, and unless they use "apt-get dist-upgrade" to upgrade to > > the newest versions of everything, packages will still be broken.
The only reason not to go to 2.1 directly is not breaking the packages in unstable.
