Message262140
| Author |
SilentGhost |
| Recipients |
SilentGhost, awilfox, docs@python, vstinner |
| Date |
2016年03月21日.16:51:51 |
| SpamBayes Score |
-1.0 |
| Marked as misclassified |
Yes |
| Message-id |
<1458579112.01.0.208963224446.issue26582@psf.upfronthosting.co.za> |
| In-reply-to |
| Content |
In fact most of the :exc: reference are pointing explicitly to concurrent.futures.CancelledError (and those that don't probably should). It is interesting that you weren't able to make use of that exception, because in Lib/asyncio/futures.py#L23 it's clearly defined as an alias of the concurrent.futures.CancelledError.
I guess, ultimately, asyncio.CancelleError needs to be documented seeing how widely used it is. |
|
History
|
|---|
| Date |
User |
Action |
Args |
| 2016年03月21日 16:51:52 | SilentGhost | set | recipients:
+ SilentGhost, vstinner, docs@python, awilfox |
| 2016年03月21日 16:51:52 | SilentGhost | set | messageid: <1458579112.01.0.208963224446.issue26582@psf.upfronthosting.co.za> |
| 2016年03月21日 16:51:51 | SilentGhost | link | issue26582 messages |
| 2016年03月21日 16:51:51 | SilentGhost | create |
|