[tonyedgecombe]

I think that post Python 3 nobody is going to do that.

It would be interesting to see a fork which removed all the crud though. Something that was easy to use for the person doing occaisional web work or beginner but without the traps and pitfalls.

[echelon]

Python 3 attempted too much change at once. The Python folks could have spread incremental rollout of the changes across several major version numbers and probably not have faced such slow adoption.

[pansa2]

> Python 3 attempted too much change at once.

Python 3 got this so, so wrong. It changed enough to break everyone's code, but not enough to make upgrading worthwhile.

It could have changed more, or changed less - done right, either would have been better than what actually happened.

[mrweasel]

I'm not sure that they could have spread it out. I believe that was the point of Python 3. Still, PHP may end up in the exact same position Python was in for the last decade, if they tried to do a similar change.

It could be worse of cause, they could end up like Perl 6 (now Raku), which makes Python 3 look like a successful transition in comparison.

[tonyedgecombe]

I thought the problem was carrying on support for 2.xx too long. Some people will never move on unless they are forced to.

[tjpnz]

>It would be interesting to see a fork which removed all the crud though.

My understanding was that some of that already exists in Hack. Although it seems they might've not gone far enough.

[ThomWilhelm3]

Good point :)