Message309894
| Author | achimnol |
|---|---|
| Recipients | achimnol, asvetlov, gvanrossum, socketpair, yselivanov |
| Date | 2018-01-13.18:03:33 |
| SpamBayes Score | -1.0 |
| Marked as misclassified | Yes |
| Message-id | <1515866614.16.0.467229070634.issue32528@psf.upfronthosting.co.za> |
| In-reply-to |
| Content | |
|---|---|
I strongly agree to have discretion of CancelledError and other general exceptions, though I don't have concrete ideas on good unobtrusive ways to achieve this. If I write my codes carefully I could control most of cancellation explicitly, but it is still hard to control it in 3rd-party libraries that I depend on. Often they just raise random errors, or CancelledError is swallowed. Also it would be nice to have some documentation and examples on how to write "cancellation-friendly" coroutine codes. |
|
| History | |||
|---|---|---|---|
| Date | User | Action | Args |
| 2018-01-13 18:03:34 | achimnol | set | recipients: + achimnol, gvanrossum, asvetlov, socketpair, yselivanov |
| 2018-01-13 18:03:34 | achimnol | set | messageid: <1515866614.16.0.467229070634.issue32528@psf.upfronthosting.co.za> |
| 2018-01-13 18:03:34 | achimnol | link | issue32528 messages |
| 2018-01-13 18:03:33 | achimnol | create | |