New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Interrupts are lost during readline PyOS_InputHook processing #47430
Comments
The (undocumented!) API for PyOS_InputHook has two defects which are This loss of interrupts can be rather annoying. The attached patch int PyOS_InputHook(int file_in); where file_in is the descriptor to monitor (PyOS_InputHook need not Testing for interruption is implemented in the HAVE_RL_CALLBACK and The attached patch was prepared against |
Michael, |
I'm unsure as to whether this is a feature request or a behaviour problem, anyone? Regardless could a core dev take a look at the patch which involves changes to the API for PyOS_InputHook, see msg68638. |
I don't understand how to reproduce the issue, there is no unit test nor a description how to reproduce the issue. I'm not aware of a bug where CTRL+c is simply ignored. CTRL+c is now well handled in Python 2.7, on Linux and Windows at least. Since the bug is now 7 years old, I just close it as out of date, sorry. |
As it happens, we just ran into the same bug.
Then Ctrl-C will not generate a KeyboardInterrupt. At first glance, the solution suggested by the original poster seems good. Can this issue by reopened? I'd be happy to take over this issue report and check the patch in more detail. |
This issue is now closed. Please open a new issue. You should mention |
I have opened a new bpo-23237 for this bug; please see |
Note: these values reflect the state of the issue at the time it was migrated and might not reflect the current state.
Show more details
GitHub fields:
bugs.python.org fields:
The text was updated successfully, but these errors were encountered: