On 11 March 2018 at 11:54, Guido van Rossum <gu...@python.org> wrote:
> Let's not play games with semantics. The way I see the situation for 2.7 > is that EOL is January 1st, 2020, and there will be no updates, not even > source-only security patches, after that date. Support (from the core devs, > the PSF, and python.org) stops completely on that date. If you want > support for 2.7 beyond that day you will have to pay a commercial vendor. > Of course it's open source so people are also welcome to fork it. But the > core devs have toiled long enough, and the 2020 EOL date (an extension from > the originally annouced 2015 EOL!) was announced with sufficient lead time > and fanfare that I don't feel bad about stopping to support it at all. > +1 from me, as even if commercial redistributors do decide they want to collaborate on a post-2020 Python 2.7 maintenance branch, there's no technical reason that that needs to live under the "python" GitHub organisation, and some solid logistical reasons for it to live somewhere more explicitly vendor managed. For example, a 2.7 vendor branch would need its own issue tracker that's independent of bugs.python.org, since the ability to report bugs against 2.7 will be removed from bpo (and all remaining 2.7-only bugs will be closed). Cheers, Nick. -- Nick Coghlan | ncogh...@gmail.com | Brisbane, Australia
_______________________________________________ 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
