concurrent.futures as_completed raise TimeoutError wrong
Open
Nobody has claimed this yet.
topic-multiprocessing
type-bug
- Dominant language
- Python
- Stars
- 77.2k
- Forks
- 36k
- PR merge metrics
- PR metrics pending
Description
| BPO | 29733 |
|---|---|
| Nosy | @MojoVampire, @jiang-wanwei |
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 2017-03-06.11:23:33.813>
labels = ['type-bug']
title = 'concurrent.futures as_completed raise TimeoutError wrong'
updated_at = <Date 2017-03-06.15:48:19.297>
user = 'https://github.com/jiang-wanwei'
bugs.python.org fields:
activity = <Date 2017-03-06.15:48:19.297>
actor = 'josh.r'
assignee = 'none'
closed = False
closed_date = None
closer = None
components = []
creation = <Date 2017-03-06.11:23:33.813>
creator = 'jiangwanwei'
dependencies = []
files = []
hgrepos = []
issue_num = 29733
keywords = []
message_count = 2.0
messages = ['289093', '289116']
nosy_count = 2.0
nosy_names = ['josh.r', 'jiangwanwei']
pr_nums = []
priority = 'normal'
resolution = None
stage = None
status = 'open'
superseder = None
type = 'behavior'
url = 'https://bugs.python.org/issue29733'
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 reading the concurrent.futures.as_completed entry point and reproduce the reported TimeoutError behavior using the issue's Python 3.6 context. Locate the existing concurrent.futures tests and establish the expected exception behavior before adding regression coverage; the issue payload does not name a file or 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
- 20/100