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 pitrou
Recipients docs@python, giampaolo.rodola, gvanrossum, pitrou, qmega, vstinner, yselivanov
Date 2014-04-28.19:20:55
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <1398712855.45.0.47796802283.issue21376@psf.upfronthosting.co.za>
In-reply-to
Content
Gasp. Perhaps concurrent.futures.TimeoutError can inherit from the standard TimeoutError? The following patch doesn't seem to disrupt the test suite:

diff --git a/Lib/concurrent/futures/_base.py b/Lib/concurrent/futures/_base.py
--- a/Lib/concurrent/futures/_base.py
+++ b/Lib/concurrent/futures/_base.py
@@ -49,7 +49,7 @@ class CancelledError(Error):
     """The Future was cancelled."""
     pass
 
-class TimeoutError(Error):
+class TimeoutError(Error, TimeoutError):
     """The operation exceeded the given deadline."""
     pass
History
Date User Action Args
2014-04-28 19:20:55pitrousetrecipients: + pitrou, gvanrossum, vstinner, giampaolo.rodola, docs@python, yselivanov, qmega
2014-04-28 19:20:55pitrousetmessageid: <1398712855.45.0.47796802283.issue21376@psf.upfronthosting.co.za>
2014-04-28 19:20:55pitroulinkissue21376 messages
2014-04-28 19:20:55pitroucreate