4 ms·

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.

hosay123 14y ago
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.
- tshepang 14y ago
  There is a tentative freeze date of 2015: http://mail.python.org/pipermail/python-dev/2013-April/125160.html http://mail.python.org/pipermail/python-dev/2013-April/12516....
- forsaken 14y ago
  I would love it if you would maintain a fork of 2.7. I'll look forward to the release!
  - tshepang 14y ago
    Why would you use/support the fork? Why not just upgrade?
    - spullara 14y ago
      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.
      - tshepang 14y ago
        "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/125160.html http://mail.python.org/pipermail/python-dev/2013-April/12516...
      - kstrauser 14y ago
        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.
      - gtaylor 14y ago
        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.
      - legutierr 14y ago
        I've been waiting for Django and PyPy, personally, and they're both comming along at a satisfactory pace, in my opinion.
        SoftwareMaven 14y ago
        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 :/).
      - acjohnson55 14y ago
        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.
      - spullara 14y ago
        Ok, I can see that people disagree, however, I point to: "Python 3.0 final was released on December 3rd, 2008"
  - hosay123 14y ago
    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
- shared4you 14y ago
  > 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?
  - hosay123 14y ago
    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
    - tshepang 14y ago
      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 http://bugs.python.org/issue10211.
- natmaster 14y ago
  http://hg.python.org/cpython/file/9290822f2280/Misc/NEWS http://hg.python.org/cpython/file/9290822f2280/Misc/NEWS does not list any new features, so no.

hosay123 14y ago

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.

tshepang 14y ago
There is a tentative freeze date of 2015: http://mail.python.org/pipermail/python-dev/2013-April/125160.html http://mail.python.org/pipermail/python-dev/2013-April/12516....
forsaken 14y ago
I would love it if you would maintain a fork of 2.7. I'll look forward to the release!
- tshepang 14y ago
  Why would you use/support the fork? Why not just upgrade?
  - spullara 14y ago
    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.
    - tshepang 14y ago
      "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/125160.html http://mail.python.org/pipermail/python-dev/2013-April/12516...
    - kstrauser 14y ago
      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.
    - gtaylor 14y ago
      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.
    - legutierr 14y ago
      I've been waiting for Django and PyPy, personally, and they're both comming along at a satisfactory pace, in my opinion.
      - SoftwareMaven 14y ago
        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 :/).
    - acjohnson55 14y ago
      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.
    - spullara 14y ago
      Ok, I can see that people disagree, however, I point to: "Python 3.0 final was released on December 3rd, 2008"
- hosay123 14y ago
  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
shared4you 14y ago
> 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?
- hosay123 14y ago
  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
  - tshepang 14y ago
    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 http://bugs.python.org/issue10211.
natmaster 14y ago
http://hg.python.org/cpython/file/9290822f2280/Misc/NEWS http://hg.python.org/cpython/file/9290822f2280/Misc/NEWS does not list any new features, so no.