2020, January 1 is Python2 end of life date, this date two years ago by "Python Father" Guido van Rossum announced that the developer community has since become a highly anticipated day.
Yesterday is this uplifting day, a variety of festive patterns changed without a break in coverage purposes. Ridicule joke a lot, like this:
And this (do not believe it!):
However, I came across today doubt a big brother, along the following lines: official website of Python2 retirement date, said in April, the countdown to the official news website is not fake?
He said the official website of the message is this -
How it happened? Pass so long New Year's retirement news, even inaccurate? So many people chattering away celebrating, turned out to be celebrating a fake news?
I searched the article, read it carefully, and then noticed the release date is December 20, 2019, that is, two weeks ago. The text did not mention January 1, did not mention a specific date in April.
The article is true, but the date apparently contradictory, this is how it happened? The official should have to explain it? With questions, I went to look at the official Twitter and a few core developers.
After some data access, I finally figure out how it happened, also find so-called "official explanation."
Brief Description Conclusion: 2020-01-01 virtual certainty Python2 the EOL (end of life, end of life) days, but is still in pre-release period of the day, the final version is scheduled in April this year Pycon published on the US Congress.
Python2.7 in the final version of the 2019 is the October 19 release of version 2.7.17, all the problems until after it generated between 2020-01-01, developers are acceptable, but the planned closing of version is 2.7.18 version of April 17.
Basketball game buzzer analogy, you will understand how it happens: the ball from the hands in the air flying a third of the journey, this time to terminate the whistle blew, this last ball in the bag of course, effective of.
进行了三分之一的 2.7.18 版本，就像离手之球，离弦之箭，泼出之水，负责任的 Python 官方还是要认可它的。
其实，这个决定并不是最近确定的，早在 2019 年 9 月，Python2 的版本经理 Benjamin Peterson 就公布了这个计划，这里是当时的邮件组截图：
有不少开发者表示了疑义：为什么不能把 4 月的发布计划提前呢？如果是 4 月发布最后版本，为什么不说 4 月才是 EOL 呢？为什么容许出现两个不一致的日期？
根据我对讨论内容的理解，主要有如下原因：
- 12 月末不是一个方便的“工作”时间（因为感恩节放假！）
- 4 月有一年一度的社区大会，届时大家可以集体宣泄
- Python 1 的最后版本（1.6.1）已经有此先例
有不少开发者也表示附议，认可这个安排。详细的讨论过程在：https://dwz.cn/ECmB3cZo
如果 PSF 在发布那篇“4 月退休”的文章时，对此安排作出解释，也许大家就不会有那么多困惑了，更不至于怀疑自己在传播假消息……
看到这，你也应该理解了来龙去脉吧？不过，我相信还是有读者有疑问：既然早就知道会有这个尾巴要处理，为什么不能加快进度，多投精力，争取一分不差地在 2019-12-31 发布最后一个版本呢？
追进度、赶 deadline、加班加点，这种事情在国内互联网领域是司空见惯了。然而，Python 核心开发者们几乎都是志愿者，花的是业余兴趣时间，他们的主业可能都不至于 996，怎么能指望在副业上 996 呢？！不要强人所难！
最后，不管怎么说，Python2 确实是在 2010-01-01 就 EOL 了，此后自生自灭。
它的最后一个版本会在 4 月份发布（只包含 1 月 1 日前的问题），我们不用着急，就让这只球飞一会吧，等到球落袋的时候，我们再一起，举杯相庆！
公众号【Python猫】， 本号连载优质的系列文章，有喵星哲学猫系列、Python进阶系列、好书推荐系列、技术写作、优质英文推荐与翻译等等，欢迎关注哦。