Hacker News new | past | comments | ask | show | jobs | submit login

The biggest change by far is to process not code: https://www.python.org/dev/peps/pep-0602/

I have mixed feelings about a 12 month development cycle. From the perspective of a library maintainer but not a core contributor, this seems like a headache to support up to five versions concurrently. I understand we want to avoid the Python 2.7 debacle, but seems pretty rapid no?




Perl has been on a 12 month development cycle so some years (since perl 5.12 i think which would be from 2010).

I seems to have worked out well but they only support the two most recent (stable) versions - https://perldoc.perl.org/perlpolicy#MAINTENANCE-AND-SUPPORT


Do you mean external library? Then you are free to choose the python versions you support.


Tox makes it easy to run the test suite on multiple versions of python.

https://tox.readthedocs.io/en/latest/


Have a look at Typescript's hectic release schedule:

- 3.1 in September 2018

- 3.2 in November 2018

- 3.3 in January 2019

- 3.4 in March 2019

- 3.5 in May 2019

- 3.6 in August 2019

- 3.7 in November 2019

- 3.8 in February 2020

- 3.9 in May 2020

- 4.0 in August 2020

I'm not saying that this doesn't cause headaches, but do we really want less progress?




Guidelines | FAQ | Lists | API | Security | Legal | Apply to YC | Contact

Search: