Join GitHub today
Finalize exception names: BrokenResourceError? BusyResourceError? #620
This isn't super urgent, but I want to make sure we revisit it before v1.0, so creating an issue that I can tag "potential API breaker".
Should we rename
Should we consolidate
Yep, I'd rename it.
I generally design exceptions by asking "what will users want to catch", so why not both? That is, define
The argument for
You meant this rhetorically, but there actually is an answer :-).
Example: suppose we have a "channel" object (#586) that's implemented on top of a
Now, while that's happening in one task, another task calls
Also, this example with channels on top of streams has kind of convinced me that we should have a single