News for hackers. Stuff that matters.
Re:Python 2.7.4 Released by gluxon on Saturday April 06, 2013 @08:01PM (#5505538)
It annoys me how this release was added to the 2.7.x line when it probably should have been 2.8 given all the changes and feature additions. Freezing the 2.x line means not making huge changes to it. Otherwise, it probably shouldn't have been frozen.
Re:Python 2.7.4 Released by natmaster on Saturday April 06, 2013 @08:03PM (#5505541)
I know it's confusing but the feature list on this page is for python 2.7; the 2.7.4 release appears to just be bugfixes.
Re:Python 2.7.4 Released by hosay123 on Saturday April 06, 2013 @08:09PM (#5505561)
You should check the changelog, they're still adding functionality by stretching the definition of 'bug fix'.. 2.x development is unlikely to freeze any time soon. I certainly have no intention of moving to 3.x, it would be the most pointless upheaval ever. I'd sooner fork 2.x and maintain it myself.
Re:Python 2.7.4 Released by shared4you on Saturday April 06, 2013 @08:36PM (#5505624)
> they're still adding functionality by stretching the definition of 'bug fix'

Can you please elaborate? All entries in the changelog start with "Fix" or "update", etc. What new functionality has been added, according to you?

Re:Python 2.7.4 Released by hosay123 on Saturday April 06, 2013 @09:14PM (#5505731)
Did you even read my other comment? Enhancing the (10 year old plus) buffer interface with functionality it has never supported does not constitute a bug fix
Re:Python 2.7.4 Released by tshepang on Saturday April 06, 2013 @09:32PM (#5505770)
Surely, even with maintenance releases, there are exceptions where developers decide to break the rules a bit? Check the justification for this specific one: http://bugs.python.org/issue10211.
Re:Python 2.7.4 Released by forsaken on Saturday April 06, 2013 @08:29PM (#5505602)
I would love it if you would maintain a fork of 2.7. I'll look forward to the release!
Re:Python 2.7.4 Released by hosay123 on Saturday April 06, 2013 @09:19PM (#5505743)
The core team are already planning how to interact with the eventual community maintained fork. It's not a question of if but when.

The only concrete attraction of 3 for me is the Unicode improvement, and even that isn't exactly compelling. 3 is practically a new language designed to solve problems I've almost never encountered. Perhaps when someone comes up with a meaningful use of annotations or a workaround for e.g. the functionality lost by the cmp removal, I might change my mind

Re:Python 2.7.4 Released by tshepang on Saturday April 06, 2013 @08:45PM (#5505653)
Why would you use/support the fork? Why not just upgrade?
Re:Python 2.7.4 Released by spullara on Saturday April 06, 2013 @08:56PM (#5505671)
It is pretty clear that the current users of Python 2.x have voted that they don't want to move to Python 3. Some language changes and lots of library changes. Everything has to be ported to upgrade.
Re:Python 2.7.4 Released by gtaylor on Saturday April 06, 2013 @11:01PM (#5505923)
As a current user of Python 2.x, I can't wait to make the jump to 3, and have already done so for a few of my personal projects. It's probably best not to generalize too much.
Re:Python 2.7.4 Released by tshepang on Saturday April 06, 2013 @09:22PM (#5505750)
"current users of Python 2.x" is too broad to be accurate; anyways, it will be interesting to watch how motivated the holdouts will be when the 2015 deadline[1] approaches.

[1]: http://mail.python.org/pipermail/python-dev/2013-April/12516...

Re:Python 2.7.4 Released by kstrauser on Saturday April 06, 2013 @10:42PM (#5505897)
I wouldn't say that at all. My company had voted that we weren't ready to move to Python 3 yet. It's looking very likely that we'll be making the leap for new development starting in the next week or so.

Python 2 is a beautiful, wonderful language. Python 3 is even better and there are very few reasons not to adopt it now.

Re:Python 2.7.4 Released by legutierr on Saturday April 06, 2013 @11:30PM (#5505994)
I've been waiting for Django and PyPy, personally, and they're both comming along at a satisfactory pace, in my opinion.
Re:Python 2.7.4 Released by SoftwareMaven on Saturday April 06, 2013 @11:43PM (#5506032)
I started a new Django project at work using Python 3. Fun part is it gives me an excuse to help some of the various Django libs to move to 3 (if the authors are still around to take pull requests :/).
Re:Python 2.7.4 Released by acjohnson55 on Sunday April 07, 2013 @02:33AM (#5506319)
I love Python 2.x, but I'll be ready to convert to 3 just as soon as the library support comes through. We're getting pretty close, I feel.
Re:Python 2.7.4 Released by spullara on Monday April 08, 2013 @12:26PM (#5512674)
Ok, I can see that people disagree, however, I point to:

"Python 3.0 final was released on December 3rd, 2008"

Re:Python 2.7.4 Released by tshepang on Saturday April 06, 2013 @08:15PM (#5505578)
There is a tentative freeze date of 2015: http://mail.python.org/pipermail/python-dev/2013-April/12516....
Re:Python 2.7.4 Released by natmaster on Saturday April 06, 2013 @08:41PM (#5505639)
http://hg.python.org/cpython/file/9290822f2280/Misc/NEWS does not list any new features, so no.
[deleted]
Re:Python 2.7.4 Released by rdtsc on Saturday April 06, 2013 @08:58PM (#5505682)
_That is the point_

"We'll stomp our feet and make a big deal about how there won't be a 2.8, then put all the 2.8 like changes in 2.7.x"