At last! Python 3.5 has now officially reached its end-of-life. Since there have been no checkins or PRs since I tagged 3.5.10, 3.5.10 will stand as the final release in the 3.5 series.
As with a similar announcement I wrote about eighteen months ago, I know we can all look back fondly on Python 3.5. 3.5 added many new asynchronous I/O programming features, the "typing" module, and even a new operator ("@"). Plus many and varied quality-of-life improvements for the Python programmer, in both the language, the library, the core implementation, and even the installers. Python 3.5.0 was the best version of the best language at the time, and since then it's gotten even better!
My thanks to all the members of the Python 3.5 release team. In alphabetical order:
My thanks also to the Python infrastructure team.
The end of Python 3.5 support also ends my tenure as a Python Release Manager. Congratulations, you survived me and my frequent mistakes! (Special shouts out to Ned and Benjamin for running around behind the scenes quietly cleaning up my messes--and not even telling me most of the time.) Rest assured that I leave you in /much/ better hands with the current crop of RMs: Ned, Łukasz, and Pablo.
One amusing note. During my tenure as a Python release manager, I had to deal with /three/ different revision control systems. Although we'd switched CPython itself to Mercurial by the time 3.4 alpha 0 was released, there were still many supporting repositories still on Subversion. (I remember having to do Subversion branch merges as part of my 3.4 release work... what a pain.) And of course these days we're on Git (-hub). This straddling of three different workflows certainly complicated the lives of us Release Managers. So, my friends, please... make up your minds! ;-)
It's been my honor to serve you,
p.s. As of today, every supported version of Python supports f-strings. The only remaining excuse for "we can't use f-strings" is no longer viable!