Message266843
| Author |
r.david.murray |
| Recipients |
SilentGhost, awilfox, docs@python, r.david.murray, vstinner, yselivanov |
| Date |
2016年06月01日.22:55:27 |
| SpamBayes Score |
-1.0 |
| Marked as misclassified |
Yes |
| Message-id |
<1464821727.45.0.149216422892.issue26582@psf.upfronthosting.co.za> |
| In-reply-to |
| Content |
ping: Victor or Yuri, do agree that asyncio.CancelledError should be documented? I know that this duality has confused me in the past as well. I don't know if having it documented would have helped me ahead of time, but at least it could have cleared up my puzzlement as to why I was seeing a concurrent.futures exception when I didn't think I was using concurrent.futures :)
I do wonder what the OPs actual problem was with catching the exception. |
|