I'm not familiar with async in Python, but creating a blocking wrapper around an async call is something I've had to do quite often in various circumstances. T

I'm not familiar with async in Python, but creating a blocking wrapper around an async call is something I've had to do quite often in various circumstances. Theoretically, you shouldn't need to do that, but in practice there's always some big legacy component that you can't rewrite to make it asynchronous. In my experience it's such a common pattern that the language should support it. But in many languages it ends up being quite complex or inelegant. Makes me feel like there's a bit of a schism between language designers and users: designers want an architecture that encourages clean code, users want duct tape.