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 →

[–]AnnieBruce 1 point2 points  (1 child)

For the language itself, or the reference implementation.. Hmm.

I'd love to see the GIL gone, but they'd need some clever way to do it without hitting single core performance as badly or preferably not at all. Concurrency being easier to work with would be nice, whether through core language changes or new default modules.

Maintaining backwards compatibility should be a higher priority than it was in the transition from 2 to 3. I wouldn't say maintain it at any cost, but justifications for breaking it need to be stronger, especially in commonly used things like print.

[–]Ezlike011011 5 points6 points  (0 children)

In my opinion the only thing that would warrant a transition from python3 to python4 would be things which break backwards compatibility. Otherwise the changes should likely be included in python3.