pyrepl messed up terminal if a signal handler expects stdin
Open
Nobody has claimed this yet.
stdlib
topic-repl
type-bug
- Dominant language
- Python
- Stars
- 77.2k
- Forks
- 35.9k
- PR merge metrics
- PR metrics pending
Description
Bug report
Bug description:
This is related to #129614 but more straightforward and irrelevant to pdb. (pdb needs this to be fixed though)
Start REPL from a terminal and do
import signal
signal.signal(signal.SIGINT, lambda s, f: input("test"))
<Ctrl+C>
Your terminal is messed up and newline won't work anymore. (Not the Python repl which will exit due to some run time error, the terminal itself is messed up)
CPython versions tested on:
CPython main branch
Operating systems tested on:
Linux
Linked PRs
- gh-138617
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by reproducing the signal-handler and input sequence in the pyrepl REPL on Linux, then review the terminal-state handling around Ctrl+C and stdin. Check linked PR #138617 for the work already underway. Done means the terminal remains usable and accepts newlines after the handler calls input().
Written by the indexing model from the issue text.
Assessment
- Tech stack
- python
- Domain
- cli
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 32/100