Chris Angelico wrote:
That's because you're not actually running anything concurrently.
Yes, I know what happens and why. My point is that for someone who *doesn't* know, simplistic attempts to explain what "await" means can be very misleading. There doesn't seem to be any accurate way of summarising it in a few words. The best we can do seems to be to just say "it's a magic word that you have to put in front of any call to a function that you defined as async". A paraphrasing of the Zen comes to mind: "If the semantics are hard to explain, it may be a bad idea." > there are
complexities to the underlying concepts that can't be hidden by any framework.
I don't entirely agree with that. I think it's possible to build a conceptual model that's easier to grasp and hides more of the underlying machinery. PEP 3152 was my attempt at doing that. Unfortunately, we seem to have gone down a fork in the road that leads somewhere else and from which there's no getting back. -- Greg -- https://mail.python.org/mailman/listinfo/python-list
