You'd be correct. The distinction is whose fault is that, the lazy Python3 core dev team or the lazy userbase? We'll just assume everyone is lazy in effort towards equality. Python3 was created without any backwards compatibility to make the core dev teams job easier, nothing more nothing less. LAZY?! Yes. That's their prerogative, but the rest of us don't have to use it either.

When I say lazy in this post, I mean simply acting on one's self-interests. Because that's what every party involved here is doing.

It's important to note the difference between Python the language, and CPython. Using Python2 doesn't mean you're using some deprecated language, there's virtually no difference. That's what made the break such a shame honestly. Moving to Python3 with new code is easy. Most people just have few great reasons to now with their existing projects.

People need to stop harassing the community and start harassing Guido van Rossum and the core dev team. Usually when people make a mistake, people fix it. GvR and his rogue band of developers have not corrected the Python3 mistake in any way. They've simply continued their mistake for so long, that people are becoming twisted thinking that it's EVERYONE ELSE who is at fault! Amazing really.

CPython2 maintenance mode is just a way for the core dev team to maintain their grip around this whole debacle. If they had the guts to dump it in 2015 they would've lost complete control of the situation. It wasn't out of compassion as they say. Because they simply removed the incentive for a 3rd party to swoop in and takeover CPython2.

Even that is backfiring now. People[0] are noticing how Python3 is turning into feature soup, which is never an improvement. Thus Python2's conservatism is starting to be seen as an asset.

As far as CPython3 being under active development, so is PyPy and it's superior to CPython. The language doesn't change too much at this point. Python is Python for the most part. When the time comes for someone on 2 to move to 3, it will be a non-issue. They're not "losing out" today in any way by acting in their best interests using 2.

Python3 has nothing that didn't already exist as a 3rd party library, nor does it have anything that doesn't exist in form of a backport.
Thus technical innovation contained within is zero.

Programmers aren't stupid. And I think the PSF folks think we are. Or just blatantly disregard the community that truly made Python what it is.

The existing Python2 community is overtly disrespected when called "lazy" and all this type of harassment that goes on. I know I'm in the majority opinion because upvotes don't lie.

I'm just a guy who likes "Python", the language. I can't blame you for not using it and honestly, what a mess Guido and his core dev team has created right?

Python is my preference but I'm not held hostage by the PSF or Python3. I use Python2, Python3, Boo, PyPy. I don't hate Python3 and don't know anyone who does. It's just no slam dunk, and that's the core development team's fault- and they may lose their battle against Python fans as a result. I do highly dislike the groupthink about Python3, with a portion of the Python community on this topic.

One more thing to add, is Python3 inevitable? No. It just fragmented the Python ecosystem. Nothing more. We all won't be on a single version again. GvR and his band of rogue developers should be ashamed of themselves. Again, change happens from the bottom up. Not top down. They failed the community and should abdicate their roles but I'm afraid their egos are too big.

[0]http://learning-python.com/books/python-changes-2014-plus.ht...