This exists to get old codebases off of Python and on to Go. Supporting 3.x only makes sense if you plan to keep writing Python, which is not likely in the cards for Youtube.
The idea is to continue to write code in Python. (...) That said, there is the possibility of rewriting bits and pieces in Go (e.g. performance critical stuff) and then call into it from Python. Sort of a hybrid approach.
Also:
I'd like to support 3.x at some point.
However:
We do iteratively rewrite components as well. We are pursuing multiple strategies.
I was about to get really excited about this and then noticed that it only supports Python 2.7. :[
alrs 25 points · Jan 2017
This exists to get old codebases off of Python and on to Go. Supporting 3.x only makes sense if you plan to keep writing Python, which is not likely in the cards for Youtube.
boa13 31 points · Jan 2017
Quoting the author of Grumpy on Hacker News:
Also:
However:
__deerlord__ 2 points · Jan 2017
Wait so, Go calls Python which calls...Go? Or am I misunderstanding this