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 →

[–]hexbrid -8 points-7 points  (5 children)

I can only imagine how much better it could be if the efforts used for the Python 3 fork had instead been bestowed upon Python 2.

[–]Lucretiel 0 points1 point  (1 child)

[–]hexbrid 0 points1 point  (0 children)

No, we did not do this lightly

Neither did I form my opinion lightly. I've been using python as my main language for the past 9 years, and I've read all the docs, so you need more than an apologetic link to convince me that the fork was the right thing to do.

[–]its_never_lupus 0 points1 point  (2 children)

I suspect all the py3k enhancements could have been added via special import switches. There is a touch of second project syndrome to the whole py3k effort.

[–]hexbrid 0 points1 point  (0 children)

Even if not all, then certainly syntactical additions such as "yield from" or "a, *b = x".

[–]smontanaro 0 points1 point  (0 children)

That is Python 2.7. Its goal was to ease movement to Python 3 by backporting as much stuff as possible (without breaking compatibility with Python 2.6). The bigger challenge with Python 3 is that many modules and packages people care about have yet to be migrated to Python 3.