<story><title>Sunsetting Python 2</title><url>https://www.python.org/doc/sunset-python-2/</url></story><parent_chain><item><author>reitzensteinm</author><text>Based on your timeline, a four year gap from &amp;quot;not yet ready to migrate&amp;quot; to &amp;quot;we won&amp;#x27;t fix security vulnerabilities&amp;quot; is very short.&lt;p&gt;Python is an open source project I&amp;#x27;ve used and contributed nothing to, so I don&amp;#x27;t have the right to be a back seat driver. Were it a commercial project and I was a customer, I would be quite upset.</text></item><item><author>jedberg</author><text>In 2015, there was no way I could have moved to Python 3.  There were too many libraries I depended on that hadn&amp;#x27;t ported yet.&lt;p&gt;In 2019, I feel pretty confident about using Python 3, having used it exclusively for about 18 months now.&lt;p&gt;For my personal use case at least, this timeline worked out well for me.  Hopefully it works out for most everyone.  I can&amp;#x27;t imagine they made this decision without at least some data backing it up.</text></item></parent_chain><comment><author>shakna</author><text>Python 2&amp;#x27;s EOL was first announced in 2008, it was extended in 2014. That&amp;#x27;s more than a decade of forewarning that this was coming down the line. A decade of Python2 receiving security fixes.&lt;p&gt;Were I a commercial customer, and had been told to switch to the new version ten years ago, then it&amp;#x27;s on me if I still have started the migration yet.</text></comment>
<story><title>Sunsetting Python 2</title><url>https://www.python.org/doc/sunset-python-2/</url></story><parent_chain><item><author>reitzensteinm</author><text>Based on your timeline, a four year gap from &amp;quot;not yet ready to migrate&amp;quot; to &amp;quot;we won&amp;#x27;t fix security vulnerabilities&amp;quot; is very short.&lt;p&gt;Python is an open source project I&amp;#x27;ve used and contributed nothing to, so I don&amp;#x27;t have the right to be a back seat driver. Were it a commercial project and I was a customer, I would be quite upset.</text></item><item><author>jedberg</author><text>In 2015, there was no way I could have moved to Python 3.  There were too many libraries I depended on that hadn&amp;#x27;t ported yet.&lt;p&gt;In 2019, I feel pretty confident about using Python 3, having used it exclusively for about 18 months now.&lt;p&gt;For my personal use case at least, this timeline worked out well for me.  Hopefully it works out for most everyone.  I can&amp;#x27;t imagine they made this decision without at least some data backing it up.</text></item></parent_chain><comment><author>PeterisP</author><text>The thing is, a four year gap is very large from the perspective of &amp;quot;should we drop everything else and prioritize porting our library to python3 right now&amp;quot;.&lt;p&gt;If the deadline wasn&amp;#x27;t 2020 but 2024, then you wouldn&amp;#x27;t get more time, simply we&amp;#x27;d be at &amp;quot;not yet ready to migrate&amp;quot; state right now, as major libraries would not have switched yet.</text></comment>