ThreadPoolExecutor with wait=True shuts down too early
Open
Nobody has claimed this yet.
3.8 (EOL)
stdlib
- Dominant language
- Python
- Stars
- 77.2k
- Forks
- 36k
- PR merge metrics
- PR metrics pending
Description
| BPO | 40093 |
|---|---|
| Nosy | @fireattack, @gaoxinge |
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-03-27.23:21:42.924>
labels = ['3.8', 'library']
title = 'ThreadPoolExecutor with wait=True shuts down too early'
updated_at = <Date 2020-04-16.08:29:21.191>
user = 'https://github.com/fireattack'
bugs.python.org fields:
activity = <Date 2020-04-16.08:29:21.191>
actor = 'fireattack'
assignee = 'none'
closed = False
closed_date = None
closer = None
components = ['Library (Lib)']
creation = <Date 2020-03-27.23:21:42.924>
creator = 'fireattack'
dependencies = []
files = []
hgrepos = []
issue_num = 40093
keywords = []
message_count = 7.0
messages = ['365194', '365259', '365261', '365269', '365270', '365298', '366582']
nosy_count = 2.0
nosy_names = ['fireattack', 'gaoxinge']
pr_nums = []
priority = 'normal'
resolution = None
stage = None
status = 'open'
superseder = None
type = None
url = 'https://bugs.python.org/issue40093'
versions = ['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 ThreadPoolExecutor entry point and the wait=True shutdown path in Python's standard library Lib component. Reproduce the reported early-shutdown behavior on Python 3.8, then use the library's existing tests to define a fix that prevents shutdown before expected work completes.
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
- 25/100