homepage

set_result/set_exception methods of an asyncio.Future raise an exception if the future is cancelled.
Attached patch adds the check in 3 remaining places.

Oh, I forgot that the change in subprocess.py (check if waiter is cancelled before setting its result) is already part of the issue #23197 which comes with an unit test.
The changes on the SSL handshake are still needed.

> Oh, I forgot that the change in subprocess.py (check if waiter is cancelled before setting its result) is already part of the issue #23197 which comes with an unit test.
Wrong, it's the issue #23173.

The sslproto.py which just has been merged has a similar issue:
 if isinstance(exc, Exception):
 if self._waiter is not None:
 self._waiter.set_exception(exc)
in _on_handshake_complete().

New changeset 42f4dfc6c6a9 by Victor Stinner in branch '3.4':
Issue #23197: On SSL handshake failure on matching hostname, check if the
https://hg.python.org/cpython/rev/42f4dfc6c6a9 

New changeset c9ad45b15919 by Victor Stinner in branch '3.4':
Issue #23197, asyncio: On SSL handshake failure, check if the waiter is
https://hg.python.org/cpython/rev/c9ad45b15919 

Ok, I commited my changes to Python 3.4, Python 3.5 and Tulip. All calls to set_result/set_exception should now be protected by a check on the future state.
There is now a new class of bugs, but it's a different issue:
https://code.google.com/p/tulip/issues/detail?id=218
I close this issue.