On 25 January 2017 at 10:19, M.-A. Lemburg <m...@egenix.com> wrote: > Perhaps making the last minor version to a major release version > as we did with 2.7 is a good approach, i.e. we'd switch the > major number when cutting an LTS release and follow similar > guidelines as we have for 2.7 for this 3.x LTS release.
It also takes about that long for *idiomatic* expectations to change - Python 2.7 code written by someone that learned Python 3 first is likely to look quite different from code written by someone that started with 1.5.2 or one of the earlier 2.x releases. Cheers, Nick. -- Nick Coghlan | ncogh...@gmail.com | Brisbane, Australia _______________________________________________ python-committers mailing list python-committers@python.org https://mail.python.org/mailman/listinfo/python-committers Code of Conduct: https://www.python.org/psf/codeofconduct/
