Martin Panter added the comment: A similar problem used to exist with asyncio.TimeoutError: Issue 21376.
There is no class called concurrent.future.Error, so I would remove that bit. Otherwise, the rest of the patch looks worthwhile. With asyncio and multiprocessing, the exception name is spelt out in full, including the module prefix. Maybe it could also be done here to be less ambiguous. When reading it with an ordinary web browser, you don’t get to see the target of the hyperlinks. On the other hand, a full “concurrent.futures.TimeoutError” is rather long and unwieldy. I’m not sure. ---------- nosy: +martin.panter _______________________________________ Python tracker <rep...@bugs.python.org> <http://bugs.python.org/issue23962> _______________________________________ _______________________________________________ Python-bugs-list mailing list Unsubscribe: https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
