Of course you may be right, but obviously I don&#x27;t think so at this time. I feel I made a smart, safe bet. I&#x27;m still writing valid 2.7 code that could be migrated to 3.x at any point if for any reason my current plan would fall through. It would be just as easy for me to migrate to 3.x as it would anyone else with 2.x codebases.<p>So far, solving CPU performance in Python and removing the GIL is pretty much the holy grail. Python2 would have to completely collapse (no signs of this) for CPython3&#x27;s ecosystem to outweigh the long-tail of libraries only on 2.x and the truly next-level dynamic language CPU performance.<p>While I am enjoying &quot;performance as a feature&quot; and GIL-free Python at the moment, I can still migrate to Python3 at any time if I lose my safe bet with PyPy4&#x2F;Py2.<p>To me it looked and still looks like a no brainer.