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 matt
Recipients gvanrossum, matt, vstinner, yselivanov
Date 2015-04-30.13:59:57
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <>
asyncio.Event.wait() doesn't seem to be cancelled by asyncio.wait_for(). Ctrl-c in the attached example produces output below. I'm not certain the code is correct though the documentation for wait_for() suggests it should work. Without the wait_for() it doesn't suffer from pending task destruction. This is Python 3.4.3. 

Hello World!
Hello World!
^CTraceback (most recent call last):
  File "./", line 27, in <module>
  File "/Library/Frameworks/Python.framework/Versions/3.4/lib/python3.4/asyncio/", line 304, in run_until_complete
  File "/Library/Frameworks/Python.framework/Versions/3.4/lib/python3.4/asyncio/", line 276, in run_forever
  File "/Library/Frameworks/Python.framework/Versions/3.4/lib/python3.4/asyncio/", line 1136, in _run_once
    event_list =
  File "/Library/Frameworks/Python.framework/Versions/3.4/lib/python3.4/", line 502, in select
    kev_list = self._kqueue.control(None, max_ev, timeout)
Task was destroyed but it is pending!
task: <Task pending coro=<wait() running at /Library/Frameworks/Python.framework/Versions/3.4/lib/python3.4/asyncio/> wait_for=<Future pending cb=[Task._wakeup()]> cb=[_release_waiter(<Future]>)() at /Library/Frameworks/Python.framework/Versions/3.4/lib/python3.4/asyncio/]>
[1]    8134 exit 1     ../venv3/bin/python3 ./
Date User Action Args
2015-04-30 13:59:58mattsetrecipients: + matt, gvanrossum, vstinner, yselivanov
2015-04-30 13:59:58mattsetmessageid: <>
2015-04-30 13:59:58mattlinkissue24080 messages
2015-04-30 13:59:57mattcreate