This issue tracker has been migrated to GitHub, and is currently read-only.
For more information, see the GitHub FAQs in the Python's Developer Guide.

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 <>
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.
Date User Action Args
2016-06-01 22:55:27r.david.murraysetrecipients: + r.david.murray, vstinner, SilentGhost, docs@python, yselivanov, awilfox
2016-06-01 22:55:27r.david.murraysetmessageid: <>
2016-06-01 22:55:27r.david.murraylinkissue26582 messages
2016-06-01 22:55:27r.david.murraycreate