Audit event for time.sleep

[Rosuav (Chris Angelico)]

@encukou

Unfortunately, as Will found out, beginner users often use time.sleep in their experiments as a substitute for doing work. “Don’t use sleep” is one async concept they need to know about – and there’s no good way to teach them.

Static analysis might help users, but it’s not useful for a framework.

That’s reasonable; in that case, I wouldn’t be averse to the framework monkeypatching a few prime targets like that, to help people notice problems.

@encukou

Avoiding other blocking things like gethostname is important for IO throughput, but AFAIK isn’t that important for UI: if an animation freezes for a millisecond, you aren’t likely to notice it.

Ahh… yes. Up until it’s not a millisecond but several seconds and your entire UI becomes completely nonresponsive. Unfortunately gethostbyname can be quite annoying to solve - your options are either bypass it and directly call on a DNS server (which forfeits the benefits of the hosts file and anything changed in nsswitch (where applicable)), or spin it off into a thread, which isn’t something people tend to stumble upon as a solution (and has its own overheads and potential issues).