Title: asyncio.wait_for() TimeoutError doesn't provide full traceback
Type: behavior Stage:
Components: asyncio, Library (Lib) Versions: Python 3.6
Status: open Resolution:
Dependencies: Superseder:
Assigned To: Nosy List: chris.jerdonek, snihalani, yselivanov
Priority: normal Keywords:

Created on 2017-08-07 11:06 by chris.jerdonek, last changed 2017-09-25 03:16 by snihalani.

Messages (2)
msg299845 - (view) Author: Chris Jerdonek (chris.jerdonek) * (Python committer) Date: 2017-08-07 11:06
In Python 3.6.1, if asyncio.wait_for() times out with a TimeoutError, the traceback doesn't show what line the code was waiting on when the timeout occurred. This makes it more difficult to diagnose the cause of a timeout.

To reproduce, you can use the following code:

    import asyncio

    async def run():
        await asyncio.sleep(1000000)

    def main(coro):
        loop = asyncio.new_event_loop()
        future = asyncio.wait_for(coro, timeout=1)


It gives the following output (notice that the sleep() line is missing):

    $ python 
    Traceback (most recent call last):
      File "", line 12, in <module>
      File "", line 10, in main
      File "/Users/.../python3.6/asyncio/", line 466,
         in run_until_complete
        return future.result()
      File "/Users/.../python3.6/asyncio/", line 356, in wait_for
        raise futures.TimeoutError()

It seems like it should be possible to show the full traceback because, for example, if I register a signal handler with loop.add_signal_handler() as described here:
and press Control-C before the timeout occurs, I do get a full traceback showing the line:

    await asyncio.sleep(1000000)
msg302909 - (view) Author: Suren Nihalani (snihalani) * Date: 2017-09-25 03:16
this'd be useful to me as well. I'd propose we pass the future in the exception object.

Can write a write a tiny patch for this if someone would approve.
Date User Action Args
2017-09-25 03:16:32snihalanisetnosy: + snihalani
messages: + msg302909
2017-08-07 11:06:35chris.jerdonekcreate