Hi Lino, Lino Mastrodomenico <l.mastrodomenico@gmail.com> (20/04/2010): > Given how much work is required to change the default Python, does > it make sense to just skip Python 2.6 and use 2.7 as the default > Python version in Squeeze? Python 2.6 transition is already going on. > The glaring downside of this is that 2.7 hasn't yet been released, > but a feature-complete beta is available and, given how big the test > suite is nowadays, it's pretty stable. The final 2.7 should be > released in June (see PEP 373 for the full schedule) which is, I > guess, before the release of Squeeze. Heard of what's called “freeze” in the release process? Hopefully, it will start before Python 2.7 is released. And the testsuite ensures basically nothing WRT Python Modules from other source packages. > Python 2.7 is faster than 2.6 (in my limited tests from a few > percents to more than 7 times faster, the latter with a small > CPU-intensive math program), it has a few cool new toys, for many > years in the future it will be THE Python 2 version (it's the last > one) and, most importantly it has several new features to make the > transition to Python 3 easier. For any software, new versions always have new shiny features and of course no regressions. > Including it in Debian now should make many Python programmers > happier in the next few years. Including it and making it the default are two different topics. > TIA for any feedback to this crazy idea. You named it. :) Mraw, KiBi.
Attachment:
signature.asc
Description: Digital signature