run pool.submit in callback when future.set_result
Open
Nobody has claimed this yet.
stdlib
type-bug
- Dominant language
- Python
- Stars
- 77.2k
- Forks
- 36k
- PR merge metrics
- PR metrics pending
Description
| BPO | 34268 |
|---|---|
| Nosy | @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 2018-07-29.03:25:08.090>
labels = ['type-bug', 'library']
title = 'run pool.submit in callback when future.set_result'
updated_at = <Date 2018-07-29.03:25:08.090>
user = 'https://github.com/gaoxinge'
bugs.python.org fields:
activity = <Date 2018-07-29.03:25:08.090>
actor = 'gaoxinge'
assignee = 'none'
closed = False
closed_date = None
closer = None
components = ['Library (Lib)']
creation = <Date 2018-07-29.03:25:08.090>
creator = 'gaoxinge'
dependencies = []
files = []
hgrepos = []
issue_num = 34268
keywords = []
message_count = 1.0
messages = ['322605']
nosy_count = 1.0
nosy_names = ['gaoxinge']
pr_nums = []
priority = 'normal'
resolution = None
stage = None
status = 'open'
superseder = None
type = 'behavior'
url = 'https://bugs.python.org/issue34268'
versions = ['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 tracing the Python library implementation behind pool.submit, Future.set_result, and their callbacks; the payload identifies the affected area only as Lib (Library). Reproduce the callback behavior described in the title and determine the expected ordering or execution semantics before identifying suitable regression coverage.
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