On Sat, Feb 3, 2018 at 10:46 PM, Ned Deily <n...@python.org> wrote: > On Feb 3, 2018, at 17:40, Alex Walters <tritium-l...@sdamon.com> wrote: > > I am still working on porting code from 2.x to 3.x. As of late on the > lists > > I've seen comments about making somewhat major changes in 4.0 - now I'm > > concerned that I should pause my porting effort until that is released. > Is > > python 4 going to be another python 3? > > At this point, Python 4 is just a convenient tag for really big changes. > There are no concrete plans or schedule for such a major undertaking. Port > away to Python 3.x! > > "Py3K?" they said, "oh, no, we're just noodling around with a few ideas ..." :-)
To be honest, and historically fair to Guido, he did warn for a long time that we should expect breaking changes in an eventual wart-removal release. It seemed to me the biggest disappointment was the team not having the resources to devote to a mooted but never really achieved reorganisation of the stdlib. Rectifying that omission would, I hope, be included as a priority in any Python 4 design. Since people rely on the stdlib hugely, automated translation of at least 98% of existing stdlib imports should be a goal. But that's just me.
_______________________________________________ Python-Dev mailing list Python-Dev@python.org https://mail.python.org/mailman/listinfo/python-dev Unsubscribe: https://mail.python.org/mailman/options/python-dev/archive%40mail-archive.com
