bpo-39239: epoll.unregister() no longer ignores EBADF#17882
bpo-39239: epoll.unregister() no longer ignores EBADF#17882vstinner merged 1 commit intopython:masterfrom vstinner:epoll_ebadf
Conversation
The select.epoll.unregister() method no longer ignores the EBADF error.
tiran
left a comment
There was a problem hiding this comment.
I don't recall why I ignored EBADF here. Victor has made a compelling argument to stop ignoring the error. I trust his judgement.
asvetlov
left a comment
There was a problem hiding this comment.
I agree with the pull request.
Silent ignoring of an error was a bad idea and looks like oversight.
|
@asvetlov: "I agree with the pull request. Silent ignoring of an error was a bad idea and looks like oversight." Do you expect EBADF errors in legit asyncio code? I don't think so. asyncio is not supposed to unregister a closed FD. I mean: I don't see why I would happen, except if the application does something wrong, no? |
You are correct. |
|
@giampaolo: "+1" Oh ok, so I wasn't the only one surprised by ignoring silently EBADF ;-) |
The select.epoll.unregister() method no longer ignores the EBADF error.
The select.epoll.unregister() method no longer ignores the EBADF
error.
https://bugs.python.org/issue39239