5 ms·
Why would you use/support the fork? Why not just upgrade?
by tshepang 14y ago
Why would you use/support the fork? Why not just upgrade?
- spullara 14y agoIt 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 agoI 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 agoAs 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 agoI've been waiting for Django and PyPy, personally, and they're both comming along at a satisfactory pace, in my opinion.
- SoftwareMaven 14y agoI 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 agoI 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 agoOk, I can see that people disagree, however, I point to: "Python 3.0 final was released on December 3rd, 2008"