IDLE shutdown glitch when started by import
Open
Nobody has claimed this yet.
topic-IDLE
topic-tkinter
type-bug
- Dominant language
- Python
- Stars
- 77.2k
- Forks
- 36k
- PR merge metrics
- PR metrics pending
Description
| BPO | 27024 |
|---|---|
| Nosy | @terryjreedy, @roseman, @serhiy-storchaka |
| Files |
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-15.05:25:46.025>
labels = ['type-bug', 'expert-tkinter']
title = 'IDLE shutdown glitch when started by import'
updated_at = <Date 2016-06-13.00:12:12.664>
user = 'https://github.com/terryjreedy'
bugs.python.org fields:
activity = <Date 2016-06-13.00:12:12.664>
actor = 'markroseman'
assignee = 'none'
closed = False
closed_date = None
closer = None
components = ['Tkinter']
creation = <Date 2016-05-15.05:25:46.025>
creator = 'terry.reedy'
dependencies = []
files = ['42857']
hgrepos = []
issue_num = 27024
keywords = ['patch']
message_count = 6.0
messages = ['265581', '265594', '265602', '265644', '268407', '268410']
nosy_count = 3.0
nosy_names = ['terry.reedy', 'markroseman', 'serhiy.storchaka']
pr_nums = []
priority = 'normal'
resolution = None
stage = 'patch review'
status = 'open'
superseder = None
type = 'behavior'
url = 'https://bugs.python.org/issue27024'
versions = ['Python 2.7', 'Python 3.5', 'Python 3.6']
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 reading tkinter_destroy_cancel_handlers.patch from the linked historical issue and trace the IDLE shutdown path it addresses. Reproduce the shutdown glitch when IDLE is started by import, then verify that the behavior is corrected without breaking Tkinter cleanup.
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
- Needs clarification
- Newbie friendliness
- 30/100