21–30 of 50 posts
Earlier quoted context omitted.
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.
I would love it if you would maintain a fork of 2.7. I'll look forward to the release!
From the main python.org homepage, I see the announcement for Python 3.3.1 as well. What's curious is... Python 3.2.4 and Python 3.3.1 final have been released. Published: Sun , 6 April 2013, 22:30 +0200 Python 2.7.4 has been released. Published: Sat , 6 April 2013, 11:00 -0500
Earlier quoted context omitted.
I would love it if you would maintain a fork of 2.7. I'll look forward to the release!
Why would you use/support the fork? Why not just upgrade?
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.
[deleted]
"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"
From the main python.org homepage, I see the announcement for Python 3.3.1 as well. What's curious is... Python 3.2.4 and Python 3.3.1 final have been released. Published: Sun , 6 April 2013, 22:30 +0200 Python 2.7.4 has been released. Published: Sat , 6 April 2013, 11:00 -0500
It seems weird that large features like dictionary comprehensions and syntax changes like set literals are making it int0 2.7.x, but I'm not complaining - most of my projects are stuck on 2.7 due to deployment environment or library limitations and I'd love to be able to use these features.
Earlier quoted context omitted.
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.
> 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?
Earlier quoted context omitted.
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.
I would love it if you would maintain a fork of 2.7. I'll look forward to the release!
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
From the main python.org homepage, I see the announcement for Python 3.3.1 as well. What's curious is... Python 3.2.4 and Python 3.3.1 final have been released. Published: Sun , 6 April 2013, 22:30 +0200 Python 2.7.4 has been released. Published: Sat , 6 April 2013, 11:00 -0500
It's not that curious, Georg Brandl is release manager for the 3.* releases, Benjamin Peterson is release manager for the 2.7.4 release and they live in different timezones.