python already forked the language once for py2 --> py3. it has taken a long time in many places for py3 to be adopted. i worked professionally with python for

python already forked the language once for py2 --> py3. it has taken a long time in many places for py3 to be adopted. i worked professionally with python for about 8 years and never once wrote a python 3 program for a client. the last enterprise i was working at that had python code would have had something like 1 million lines of custom python 2 code last year, and was showing no signs of slowing down, or thinking about porting to python 3. it is arguably not a winning move to make another backwards incompatible change to the language. a lot of the value is in the ecosystem of existing useful libraries. one of the things i like about go - ease of deployment - is more irritating with python. but: once you have set up a pipeline for deploying your python code, then you're good. it's not really like the python language needs to be reengineered to compile into a single statically linked binary to make it possible to ship. these days there are containers and so forth, and historically a number of bundling and packaging tools for python apps have been available. i would still pick python over go any day for prototyping algorithmic or numeric code -- it is a terser and more expressive language for computing things, and python's dynamic typing + duck typing lets you write syntactically generic code.