Yes, I could do that. But as it is, I&#x27;m no worse off than anyone else with Python2 codebases.<p>I used to use the future imports and the things you&#x27;re suggesting but since my job is Python2.x I stopped. I prefer to just keep my head there all the time. If I were to migrate to CPython3 instead of PyPy4 as I&#x27;ve done, it would be a wholesale move. Employer moves, I move. The underlying incentives aren&#x27;t there though at the moment for either of us.<p>I&#x27;m certainly not going to push my employer into something that isn&#x27;t in their best-interests (or mine, work for nothing). If anything, they need to move to PyPy for the same reasons I did.<p>Py3 needs a bigger ecosystem than 2.x, needs an answer to PyPy4&#x27;s CPU performance and removal of the GIL, and convince employers it&#x27;s better than CPython2 and&#x2F;or PyPy4. 
Those are 4 potentially insurmountable tasks.<p>The best thing to do is start removing features rather than adding them, such as this 4th string formatting method in 3.6. It (Python3) is just very unappealing.