➜
This issue tracker has been migrated to GitHub,
and is currently read-only.
For more information,
see the GitHub FAQs in the Python's Developer Guide.
Created on 2003-06-27 14:22 by kdart, last changed 2022-04-10 16:09 by admin. This issue is now closed.
| Files | ||||
|---|---|---|---|---|
| File name | Uploaded | Description | Edit | |
| python_readline.diff | kdart, 2003-06-27 14:22 | readline diff | ||
| Messages (4) | |||
|---|---|---|---|
| msg44127 - (view) | Author: Keith Dart (kdart) | Date: 2003-06-27 14:22 | |
Attached is a patch against the readline module that hooks the readline event hook to call the PyErr_CheckSignals(). This way, Python signal handlers get run even if you are sitting at a readline prompt (where they didn't before). this solves a long-standing annoyance for me. whew. |
|||
| msg44128 - (view) | Author: Guido van Rossum (gvanrossum) *  |
Date: 2003-06-30 16:22 | |
Logged In: YES user_id=6380 Sorry, I don't think this is correct. The code ignores errors from PyErr_CheckSignals(). What will happen to an exception raised by the handler call? |
|||
| msg55406 - (view) | Author: Skip Montanaro (skip.montanaro) *  |
Date: 2007-08-29 01:52 | |
kdart - do you have any response to Guido's question? |
|||
| msg59172 - (view) | Author: Christian Heimes (christian.heimes) * |
Date: 2008-01-03 23:18 | |
In Python 2.6 the readline module does check for signals. |
|||
| History | |||
|---|---|---|---|
| Date | User | Action | Args |
| 2022-04-10 16:09:28 | admin | set | github: 38723 |
| 2008-01-03 23:18:34 | christian.heimes | set | status: open -> closed nosy: + christian.heimes resolution: out of date messages: + msg59172 |
| 2007-08-29 01:52:09 | skip.montanaro | set | nosy:
+ skip.montanaro messages: + msg55406 |
| 2003-06-27 14:22:29 | kdart | create | |