Rietveld Code Review Tool
Help | Bug tracker | Discussion group | Source code | Sign in
(15064)

Issue 107170043: Deny closing a running event loop

Can't Edit
Can't Publish+Mail
Start Review
Created:
9 years, 10 months ago by haypo_gmail
Modified:
9 years, 10 months ago
Reviewers:
saghul
CC:
haypo_gmail
Visibility:
Public.

Description

Deny closing a running event loop

Patch Set 1 #

Total comments: 3
Unified diffs Side-by-side diffs Delta from patch set Stats (+14 lines, -3 lines) Patch
M asyncio/base_events.py View 1 chunk +2 lines, -0 lines 0 comments Download
M asyncio/proactor_events.py View 1 chunk +1 line, -1 line 2 comments Download
M asyncio/selector_events.py View 1 chunk +1 line, -1 line 1 comment Download
M asyncio/unix_events.py View 1 chunk +1 line, -1 line 0 comments Download
M tests/test_events.py View 1 chunk +9 lines, -0 lines 0 comments Download

Messages

Total messages: 2
saghul
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#newcode358 asyncio/proactor_events.py:358: super().close() Shouldn't super().close() already cover returningearly if the loop ...
9 years, 10 months ago (2014-06-17 08:24:10 UTC) #1
haypo_gmail
9 years, 10 months ago (2014-06-17 08:49:41 UTC) #2
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.
Sign in to reply to this message.

Powered by Google App Engine
RSS Feeds Recent Issues | This issue
This is Rietveld f62528b