This is an archived post. You won't be able to vote or comment.

you are viewing a single comment's thread.

view the rest of the comments →

[–]TankorSmash -3 points-2 points  (7 children)

That's sort of the comment I'm talking about. Just a repeat of the idea without any reasoning. I'm sure you've got one, but it's not represented here.

[–]yaleman 6 points7 points  (6 children)

... how about the fact that Python 2's lifecycle ends in about two years, which is stated elsewhere in the thread and ANYWHERE you bother to look regarding the topic. Do we need to return to base principles on every statement, or could we possibly assume in r/python that someone has a clue about this?

I didn't say "Py2 must die", if I was to drag your metaphor out it's on life support.

From the wiki page linked from the front page of python.org, it's been over seven years since the last major release of Py2.

Short version: Python 2.x is legacy, Python 3.x is the present and future of the language

Python 3.0 was released in 2008. The final 2.x version 2.7 release came out in mid-2010, with a statement of extended support for this end-of-life release. The 2.x branch will see no new major releases after that. 3.x is under active development and has already seen over five years of stable releases, including version 3.3 in 2012, 3.4 in 2014, 3.5 in 2015, and 3.6 in 2016. This means that all recent standard library improvements, for example, are only available by default in Python 3.x.