Interpreter exit blocks waiting for ThreadPoolExecutor.map
Open
Nobody has claimed this yet.
3.7 (EOL)
3.8 (EOL)
stdlib
type-bug
- Dominant language
- Python
- Stars
- 77.2k
- Forks
- 36k
- PR merge metrics
- PR metrics pending
Description
| BPO | 42409 |
|---|---|
| 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-11-19.15:02:33.692>
labels = ['3.7', '3.8', 'type-bug', 'library']
title = 'Interpreter exit blocks waiting for ThreadPoolExecutor.map'
updated_at = <Date 2020-11-19.15:13:12.214>
user = 'https://bugs.python.org/gsakkis'
bugs.python.org fields:
activity = <Date 2020-11-19.15:13:12.214>
actor = 'stefosgiwrgos'
assignee = 'none'
closed = False
closed_date = None
closer = None
components = ['Library (Lib)']
creation = <Date 2020-11-19.15:02:33.692>
creator = 'gsakkis'
dependencies = []
files = ['49608']
hgrepos = []
issue_num = 42409
keywords = []
message_count = 1.0
messages = ['381433']
nosy_count = 2.0
nosy_names = ['gsakkis', 'stefosgiwrgos']
pr_nums = []
priority = 'normal'
resolution = None
stage = None
status = 'open'
superseder = None
type = 'behavior'
url = 'https://bugs.python.org/issue42409'
versions = ['Python 3.6', 'Python 3.7', 'Python 3.8']
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 with the attached threadpool_map.py and the ThreadPoolExecutor.map entry point, then reproduce the interpreter-exit behavior described in the issue. Done means the reported exit blocking no longer occurs and the relevant behavior is covered by a regression test.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- python
- Domain
- backend
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 32/100