There are also concurrent.futures.TimeoutError and multiprocessing.TimeoutError asyncio.TimeoutError is mimic to former.
On Wed, Jan 29, 2014 at 5:21 PM, Gustavo Carneiro <[email protected]> wrote: > I made a mistake now of having some code catch TimeoutError, while the Tulip > code raises asyncio.TimeoutError, and they are not the same thing. > > Is there anything that can be done to improve this? Surely the builtin > TimeoutError is good enough, or at least we should subclass it? > > > -- > Gustavo J. A. M. Carneiro > Gambit Research LLC > "The universe is always one step beyond logic." -- Frank Herbert -- Thanks, Andrew Svetlov
