On Tue, Dec 19, 2006 at 11:17:03AM -0800, Thomas Bushnell BSG wrote: > The python team has apparently decreed that python 2.3 will not be in > etch. This forces every package to use the new version. Surely it is > too late in the release cycle to be risking regressions in this way?
The python team has expressed concern about the security supportability of python2.3 in etch. Extension packages built with the current version of python-all-dev and friends already have no support for python2.3; shipping python2.3 in stable for the benefit of a handful of reverse dependencies is a genuine concern, particularly when those reverse-deps work just fine with python 2.4. And as noted, the gnucash build failure was not a regression introduced by this NMU, it was a bug in the build environment. -- Steve Langasek Give me a lever long enough and a Free OS Debian Developer to set it on, and I can move the world. [EMAIL PROTECTED] http://www.debian.org/ -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
