Code that will break in Python 4
Guido has stated to not compare semver in the past.[0]<p>Will there be a 3.10 or go to 4.0 after 3.9, per one of his core developers?[1] It&#x27;s hard to tell with Python&#x27;s leadership (no intentional mockery of the term leadership).<p>My guess is that they&#x27;ll indeed push onwards to Python4 as soon as possible. This being another attempt to make Python2 look as old and crufty as possible. 
&quot;You&#x27;re still on Python2? Wow, I&#x27;m on 4!&quot;. That&#x27;s the type of political and psychological game the Python core dev team has been playing since 2008 with 3&#x27;s release. Right alongside the 2020 EOL, another political move. Even though Python 2.7.&#x27;10&#x27; was never supposed to exist but they went back on that.<p>This because Python3 is mere technical churn, it is not true technical innovation.<p>The issue here is really one with the Python core development team. They have also adopted every niche feature into Python3 by whoever came along to ask for it.[2] This was done for the same reasons as the relative rush to rebrand the failed 3.x branch as 4. An attempt to stir up any hype possible for 3.0+.<p>They got so much wrong with Python3. Feature soup, unicode, and performance losses over 2. Unicode-by-default is the big deal and they didn&#x27;t even get that right. They simply remapped unicode to str. Which for such a big breaking change, should&#x27;ve been UTF8 alongside other new languages such as Go.[3] But it&#x27;s worse than that, Python3&#x27;s feature soup continues in 3.6 there will likely be a 4th string formatting option[4] among throwing everything they can against the wall to see what sticks (while bloating the supposedly simple, &quot;beginners&quot; language).<p>While Python2 has been riding high in popularity[5], it has absolutely nothing to do with Python3. It&#x27;s in spite of it.<p>There&#x27;s good reason the core dev team &quot;extended support&quot; for 2.7. It&#x27;s because they really did create a new, much less successful language and would&#x27;ve lost complete control of Python had they not done it.<p>Python3 is a language that looks mostly like Python, but is Python in name-only. Worse of all, it doesn&#x27;t stand on it&#x27;s own two feet with technical merits. I would personally recommend sticking with 2 until 3 ever makes sense, or finding something else to use like Swift or Go.<p>Unlike a web browser or another piece of software, the &quot;latest version&quot; of a programming language is not always in the end-user&#x27;s best interests.<p>[0]<a href="https:&#x2F;&#x2F;twitter.com&#x2F;gvanrossum&#x2F;status&#x2F;583346987925278720" rel="nofollow">https:&#x2F;&#x2F;twitter.com&#x2F;gvanrossum&#x2F;status&#x2F;583346987925278720</a><p>[1]<a href="http:&#x2F;&#x2F;www.curiousefficiency.org&#x2F;posts&#x2F;2014&#x2F;08&#x2F;python-4000.html" rel="nofollow">http:&#x2F;&#x2F;www.curiousefficiency.org&#x2F;posts&#x2F;2014&#x2F;08&#x2F;python-4000.h...</a><p>[2]<a href="http:&#x2F;&#x2F;learning-python.com&#x2F;books&#x2F;python-changes-2014-plus.html#coroutines35" rel="nofollow">http:&#x2F;&#x2F;learning-python.com&#x2F;books&#x2F;python-changes-2014-plus.ht...</a><p>[3]<a href="http:&#x2F;&#x2F;lucumr.pocoo.org&#x2F;2014&#x2F;5&#x2F;12&#x2F;everything-about-unicode&#x2F;" rel="nofollow">http:&#x2F;&#x2F;lucumr.pocoo.org&#x2F;2014&#x2F;5&#x2F;12&#x2F;everything-about-unicode&#x2F;</a><p>[4]<a href="https:&#x2F;&#x2F;www.python.org&#x2F;dev&#x2F;peps&#x2F;pep-0498&#x2F;" rel="nofollow">https:&#x2F;&#x2F;www.python.org&#x2F;dev&#x2F;peps&#x2F;pep-0498&#x2F;</a><p>[5]<a href="http:&#x2F;&#x2F;www.tiobe.com&#x2F;index.php&#x2F;content&#x2F;paperinfo&#x2F;tpci&#x2F;index.html" rel="nofollow">http:&#x2F;&#x2F;www.tiobe.com&#x2F;index.php&#x2F;content&#x2F;paperinfo&#x2F;tpci&#x2F;index....</a>