> no end in sight for Python 2.7 That's not correct. Numpy, for example, will not be supporting python2.7 starting January 1st, 2020 (https://docs.scipy.org/do

> no end in sight for Python 2.7 That's not correct. Numpy, for example, will not be supporting python2.7 starting January 1st, 2020 (https://docs.scipy.org/doc/numpy-1.14.2/neps/dropping-python2.7-proposal.html https://docs.scipy.org/doc/numpy-1.14.2/neps/dropping-python...), and there are others in the process. Python itself will stop supporting 2.7 on January 1st, 2020. (see https://devguide.python.org/#status-of-python-branches https://devguide.python.org/#status-of-python-branches) Has it been poorly managed? Yes. Will a number of companies skip upgrading from python2 to python3 and instead rewrite it in Go or Rust? Absolutely. But "no end in sight" is not an accurate depiction of the current state of affairs.