IDLE restarts when one debugs code raising SystemExit
Open
Nobody has claimed this yet.
topic-IDLE
type-bug
- Dominant language
- Python
- Stars
- 77.2k
- Forks
- 36k
- PR merge metrics
- PR metrics pending
Description
| BPO | 26949 |
|---|---|
| Nosy | @terryjreedy, @pppery, @mlouielu |
| PRs |
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:
assignee = None
closed_at = None
created_at = <Date 2016-05-04.12:49:03.499>
labels = ['expert-IDLE', 'type-bug', '3.9']
title = 'IDLE restarts when one debugs code raising SystemExit'
updated_at = <Date 2019-09-20.20:57:18.028>
user = 'https://github.com/pppery'
bugs.python.org fields:
activity = <Date 2019-09-20.20:57:18.028>
actor = 'terry.reedy'
assignee = 'none'
closed = False
closed_date = None
closer = None
components = ['IDLE']
creation = <Date 2016-05-04.12:49:03.499>
creator = 'ppperry'
dependencies = []
files = []
hgrepos = []
issue_num = 26949
keywords = []
message_count = 9.0
messages = ['264861', '264863', '264867', '265097', '265101', '294124', '294125', '294775', '352889']
nosy_count = 3.0
nosy_names = ['terry.reedy', 'ppperry', 'louielu']
pr_nums = ['1711']
priority = 'normal'
resolution = None
stage = 'test needed'
status = 'open'
superseder = None
type = 'behavior'
url = 'https://bugs.python.org/issue26949'
versions = ['Python 3.9']
Linked PRs
- gh-141328
- gh-157566
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 IDLE debugging scenario with code that raises SystemExit, then review the linked work in python/cpython#1711, gh-141328, and gh-157566. Done means IDLE no longer restarts when that debugging case occurs, with the relevant behavior covered by tests if the linked work identifies them.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- python
- Domain
- desktop
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 25/100