failed pickle hangs python on exit in CMD.exe only
Nobody has claimed this yet.
Assessment
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Newbie friendliness
- 15/100
- Issue type
- Bug
- Clarity
- Mostly clear
- Activity status
- Stale
- Tech stack
- python
- Domain
- operating-systems
Research direction
Run mp_hang.py in Windows CMD.exe to reproduce the reported hang, then read the issue discussion and PR #23290. Done means the failed pickle case no longer hangs Python while exiting from CMD.exe, with the relevant behavior verified.
Written by the indexing model from the issue text.
Description
| BPO | 42178 |
|---|---|
| Nosy | @pfmoore, @pitrou, @tjguk, @zware, @eryksun, @zooba, @applio, @cmcmarrow, @John-Ted |
| PRs | |
| 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 2020-10-27.20:52:33.937>
labels = ['OS-windows', 'type-crash', '3.9']
title = 'failed pickle hangs python on exit in CMD.exe only'
updated_at = <Date 2020-11-16.18:29:48.700>
user = 'https://github.com/cmcmarrow'
bugs.python.org fields:
activity = <Date 2020-11-16.18:29:48.700>
actor = 'eryksun'
assignee = 'none'
closed = False
closed_date = None
closer = None
components = ['Windows']
creation = <Date 2020-10-27.20:52:33.937>
creator = 'charles.mcmarrow.4'
dependencies = []
files = ['49543']
hgrepos = []
issue_num = 42178
keywords = ['patch']
message_count = 3.0
messages = ['379803', '379816', '381138']
nosy_count = 9.0
nosy_names = ['paul.moore', 'pitrou', 'tim.golden', 'zach.ware', 'eryksun', 'steve.dower', 'davin', 'charles.mcmarrow.4', 'John-Ted']
pr_nums = ['23290']
priority = 'normal'
resolution = None
stage = 'patch review'
status = 'open'
superseder = None
type = 'crash'
url = 'https://bugs.python.org/issue42178'
versions = ['Python 3.9']
- Dominant language
- Python
- Stars
- 77.2k
- Forks
- 36k
- Avg merge
- 1d 9h
- Merged PRs (30d)
- 558
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.
More from python/cpython
-
docs pending
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
-
stdlib type-feature
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
-
stdlib type-feature
Difficulty 2/5 1-3 hours Newbie friendliness 72/100
-
build type-bug
Difficulty 2/5 1-3 hours Newbie friendliness 76/100
-
stdlib topic-email type-feature
Difficulty 2/5 1-3 hours Newbie friendliness 70/100
Similar issues
-
Difficulty 2/5 1-3 hours Newbie friendliness 82/100
-
Difficulty 2/5 1-3 hours Newbie friendliness 84/100
-
Difficulty 2/5 1-3 hours Newbie friendliness 68/100
-
Difficulty 2/5 1-3 hours Newbie friendliness 86/100
-
🐛 Bug 🔔 Pending processing
Difficulty 2/5 1-3 hours Newbie friendliness 84/100
jumpserver/jumpserver#17584 ·