Message261911
| Author |
awilfox |
| Recipients |
awilfox, docs@python |
| Date |
2016年03月17日.14:45:53 |
| SpamBayes Score |
-1.0 |
| Marked as misclassified |
Yes |
| Message-id |
<1458225953.38.0.399231880747.issue26582@psf.upfronthosting.co.za> |
| In-reply-to |
| Content |
In the 3.5 and 3.6a0 documentation for asyncio, "CancelledError" is linked to the concurrent.futures.CancelledError. This led me to try catching that exception and finding that it did not work correctly at all. Only after searching for asyncio example code and seeing how other people caught asyncio.CancelledError did I realise the issue.
The fact asyncio.CancelledError even exists isn't actually documented, and I believe that is why the :exc: reference is linking to the wrong module. |
|
History
|
|---|
| Date |
User |
Action |
Args |
| 2016年03月17日 14:45:53 | awilfox | set | recipients:
+ awilfox, docs@python |
| 2016年03月17日 14:45:53 | awilfox | set | messageid: <1458225953.38.0.399231880747.issue26582@psf.upfronthosting.co.za> |
| 2016年03月17日 14:45:53 | awilfox | link | issue26582 messages |
| 2016年03月17日 14:45:53 | awilfox | create |
|