Google isn't going to "kill" Python 3. This is a relatively niche use case (grumpy only converts Python 2.7 code into Go code, and it's not 1:1 as it's missing features like decorators), and there doesn't seem to be any intention on adding new Python features into grumpy. My guess is that this was made more for Google's purposes of migrating some of their legacy Python 2.7 code to Go, in an effort to move towards Go internally. It also doesn't run Python code directly, it trans-compiles Python to Go code, which wouldn't work for some workflows. For this to have any possibility of becoming another Python runtime, it would at the very minimum have to support every feature or have a real reason to not support the specific feature in Python 2.7.<p>The other thing, arguably more important, is that there isn't really a community around grumpy, whereas there is around Python 3 (the latest nontrivial commit was 3 weeks ago for grumpy, whereas the latest nontrivial commit was 6 hours ago for Python). Even if Google did try to build a community, many people worry that Google will just abandon software when they want to, so people would be hesitant to work with this software long term, which means developers wouldn't want to build any software for it; the majority of developers developing new Python code are doing it in Python 3, and those that aren't are most likely using six rather than only 2.7 unless they're supporting a legacy codebase that either they don't want to or cannot upgrade to Python 3 or to upgrade using the six library.<p>Python 3 may, however unlikely, "die", but this and Google won't be the death of it.