I was just recently writing a somewhat complex websocket client API in both Go and Python. They were both a bit tricky, but Go's support for goroutines and channels as the concurrency primitives right in the language made the solution much more obvious. With Python, I had to figure out how to do concurrency and communication: threads, async/await, queue.Queue, something else? Go also has much better interfaces for I/O with its io.Reader and io.Writer, whereas in Python you have a "file-like object" or maybe types.TextIO if you're lucky (but is the file-like object a reader or a writer?).

So even though neither Python nor Go have websocket support in their standard libraries, it was much more obvious in Go how to do concurrency and what form the readers/writers should take.

In short, Go has good concurrency primitives baked into the language, and a much better-designed and cohesive standard library (Python's was designed over the past 30 years by a much larger collection of people; it's more bazaar than cathedral, with all the pros and cons that come with that).