https://codereview.appspot.com/107170043/diff/1/asyncio/proactor_events.py File asyncio/proactor_events.py (right): https://codereview.appspot.com/107170043/diff/1/asyncio/proactor_events.py#ne... asyncio/proactor_events.py:358: super().close() Shouldn't super().close() already cover returningearly if the loop was closed? https://codereview.appspot.com/107170043/diff/1/asyncio/selector_events.py File asyncio/selector_events.py (right): https://codereview.appspot.com/107170043/diff/1/asyncio/selector_events.py#ne... asyncio/selector_events.py:60: super().close() Ditto.
https://codereview.appspot.com/107170043/diff/1/asyncio/proactor_events.py File asyncio/proactor_events.py (right): https://codereview.appspot.com/107170043/diff/1/asyncio/proactor_events.py#ne... asyncio/proactor_events.py:358: super().close() On 2014/06/17 08:24:10, saghul wrote: > Shouldn't super().close() already cover returningearly if the loop was closed? super().close() does nothing if the event loop is already close, but it doesn't avoid to call _close_self_pipe() in this function for example.