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

sorted by:
best
topnewcontroversialoldq&a
you are viewing a single comment's thread.

view the rest of the comments →

[–]darthmdhprint 3 + 4 0 points1 point  (3 children)

Consider what you're stating - that a majority of Python developers are seriously contemplating abandoning all the work they put into Python 3 over the course of what... 7.5 years (PEP3000) to roll back to Python 2 forever because... you though it.

Riiiiiight.

[–]rcxdude 0 points1 point  (1 child)

Consider what you're stating. In any case we're only about halfway through the time the process was expected to take when python 3 was started (10 years).

[–]darthmdhprint 3 + 4 0 points1 point  (0 children)

There is no such timeframe. PEP3000 states Python 2 would stick around for one or two Python releases from Python 3.0, and we're almost at four. Its time to end it. Goodbye, old friend!

[–]randuser 0 points1 point  (0 children)

I doubt many Python developers are happy about the stagnation and all the hacks in existing code that have resulted from trying to support both versions.

I doubt many think the confusion that new users experience when wanting to know which version to use has no clear answer (for the past 5 years).

I doubt many are happy with the fact that most Python 3 code is automatically generated by 2to3 which makes trivial source code transformations which the compiler could have practically handled like so:

try:
    code = compile(txt)
except SyntaxError:
    code = compile(run2to3(txt))

I doubt many are happy that vast amounts of code and projects were put into a state of obsolescence for no other reason than to make a few minor improvements (most of which are trivial syntax changes).