Then well ok, the answer to "What did Python 3 bring to the Python community?" becomes "Yeah it ended up driving a lot of people away", which I am sure wasn't the intended purpose of Python 3.0
benefit(2->3 + performance benefit + maintainability) <
benefit(2->Go + performance benefit + maintainability)
The time cost of 2->3 will be less but if I know I will get better memory footprint, and faster response times I might be willing to invest some more time into it.
Or another way to look at it, once one sits down and rolls their sleeves looking to re-factor/renew/refresh the code base there is a good chance they will look around them and see what else is out there.
It's also quite an issue for COTS software - sometimes to jump forwards and clean up APIs they have to do a huge refactor, sometime even a re-write of the API. If this is troublesome enough, it's worth taking the time to look into the competition.
GIL only exists on CPython, there are other implementations.
PyPy is not really a good example here. It is still highly experimental, takes long time to compile, it's not compatible with quite a few libraries in normal Python, and still has all relative downsides of dynamic typing. To be frank, I don't get the point of using PyPy instead of Go.
Previously most Python libraries already use C to optimize critical components. If you can use just one language to get similar performance, why do you bother using two then?
Sounds like a good topic for a post (or at least a link - hint, hint).
Or do you mean some other style of concurrency primitives?