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.
The End Of Life date (EOL, sunset date) for Python 2.7 has been moved
five years into the future, to 2020. This decision was made to clarify
the status of Python 2.7 and relieve worries for those users who
cannot yet migrate to Python 3. See also PEP
466.
This declaration does not guarantee that bugfix releases will be made
on a regular basis, but it should enable volunteers who want to
contribute bugfixes for Python 2.7 and it should satisfy vendors who
still have to support Python 2 for years to come.
2018年3月,Python发明家Guido van Rossum评论道:
来源:https://mail.python.org/pipermail/python-dev/2018-March/152348.html
阅读第二段(强调我的):
来源:https://www.python.org/dev/peps/pep-0373/
换句话说,维护人员将不再发布2.7的任何改进或补丁,而只关注3.x。在
相关问题 更多 >
编程相关推荐