3 ms·
As far as I'm concerned (as a CPython developer), the 2.x branch can live as long as necessary. There is no reason to play games trying to push people to upgrad
by nas 17y ago
As far as I'm concerned (as a CPython developer), the 2.x branch can live as long as necessary. There is no reason to play games trying to push people to upgrade to 3.x. Those tactics piss people off and for good reason.
That said, I don't see this as a tactic to get people to upgrade. Python is an open source project and the developers get to choose what they will work on. If the Unladen Swallow guys want to merge into 3.x, that's their right. If someone else steps up to merge it into 2.x and support it, that's their right too.
Myself, I'm going to continue to fix bugs in the 2.x stream for the foreseeable future. I do plan on moving my applications to 3.x eventually though.
- jnoller 17y agoAs a Cpython developer; you and I both know 2.7 is slated to be the final "big" release of python 2.x. Anything past that point will be only bug fix/security fixes. Unladen would require a whole new 2.x release, which is not, and more than likely will not be planned. We're not playing games, we're putting features into 3k knowing full well we plan on putting 2.x out to pasture. We're making the selling points of Py3k porting much more compelling to library/framework/etc authors. If someone wants to fork 2.7 and merge it with unladen, or better yet simply run the 2.x release of unladen-swallow up on google code, that's totally their prerogative, and I know some people will. From a feature standpoint though, this is a good think for 3k as it sits today.