Looks good and useful to me; there is one question re windows part though. https://codereview.appspot.com/113700043/diff/1/asyncio/windows_events.py ...
9 years, 8 months ago
(2014-08-25 15:43:51 UTC)
#1
https://codereview.appspot.com/113700043/diff/1/asyncio/windows_events.py File asyncio/windows_events.py (right): https://codereview.appspot.com/113700043/diff/1/asyncio/windows_events.py#newcode124 asyncio/windows_events.py:124: self._loop.call_exception_handler(context) On 2014/08/25 15:43:51, yselivanov wrote: > Shouldn't you ...
9 years, 8 months ago
(2014-08-25 15:58:33 UTC)
#2
https://codereview.appspot.com/113700043/diff/1/asyncio/windows_events.py
File asyncio/windows_events.py (right):
https://codereview.appspot.com/113700043/diff/1/asyncio/windows_events.py#new...
asyncio/windows_events.py:124: self._loop.call_exception_handler(context)
On 2014/08/25 15:43:51, yselivanov wrote:
> Shouldn't you have a 'return' or 'raise' statement here?
>
> Before your change the code execution would have stopped at this point, not
you
> call 'call_exception_handler()' and it continues.
If _overlapped.UnregisterWait() raises an exception, I don't think that you can
do anything useful. The best we can do is to log an error.
Clearing attributes is a deliberate choice. See
_OverlappedFuture._cancel_overlapped() which has the same implementation.
Issue 113700043: Log more errors
Created 9 years, 9 months ago by haypo_gmail
Modified 9 years, 8 months ago
Reviewers: yselivanov
Base URL:
Comments: 2