No breaking change was required for that. :) The PyPy guys have removed the GIL with existing Python2 code.[0] The CPython core dev team doesn&#x27;t want to work that hard though- they&#x27;ve just created a lot of needless work for others with their decisions.<p>You&#x27;re right though, unless someone takes on the mantle of CPython2, we&#x27;re looking at being forced to move to 3 or find something else. I personally think &#x27;16&#x2F;&#x27;17 will be the year(s) of Swift. With the Perfect server-side Swift framework[1], and more sure to come, it&#x27;s very intriguing.<p>I&#x27;m a pretty conservative user myself, and dislike churn and feature bloat so I&#x27;m also fairly attracted to Go. I&#x27;m not suggesting that&#x27;s Swift by any means. Go promised no breaking changes for a long time so it&#x27;s a good choice to write long-lived software in (and who knows what will and won&#x27;t end up being long-lived so we should always assume the latter).<p>[0]<a href="http:&#x2F;&#x2F;morepypy.blogspot.com&#x2F;2015&#x2F;03&#x2F;pypy-stm-251-released.html" rel="nofollow">http:&#x2F;&#x2F;morepypy.blogspot.com&#x2F;2015&#x2F;03&#x2F;pypy-stm-251-released.h...</a><p>[1]<a href="http:&#x2F;&#x2F;perfect.org&#x2F;" rel="nofollow">http:&#x2F;&#x2F;perfect.org&#x2F;</a>