Trying to cleanly terminate a threaded Queue at exit of program raises an "EOFError"
Open
Nobody has claimed this yet.
stdlib
topic-multiprocessing
type-bug
- Dominant language
- Python
- Stars
- 77.2k
- Forks
- 36k
- Avg merge
- 1d 9h
- Merged PRs (30d)
- 558
Description
| BPO | 33076 |
|---|---|
| Nosy | @Delgan |
| 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 2018-03-14.21:14:36.670>
labels = ['type-bug', 'library']
title = 'Trying to cleanly terminate a threaded Queue at exit of program raises an "EOFError"'
updated_at = <Date 2018-03-14.21:14:36.670>
user = 'https://github.com/Delgan'
bugs.python.org fields:
activity = <Date 2018-03-14.21:14:36.670>
actor = 'Delgan'
assignee = 'none'
closed = False
closed_date = None
closer = None
components = ['Library (Lib)']
creation = <Date 2018-03-14.21:14:36.670>
creator = 'Delgan'
dependencies = []
files = ['47486']
hgrepos = []
issue_num = 33076
keywords = []
message_count = 1.0
messages = ['313841']
nosy_count = 1.0
nosy_names = ['Delgan']
pr_nums = []
priority = 'normal'
resolution = None
stage = None
status = 'open'
superseder = None
type = 'behavior'
url = 'https://bugs.python.org/issue33076'
versions = ['Python 3.5', '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 running the attached bug.py reproduction and confirm the EOFError during threaded Queue shutdown. Then trace the relevant Python library implementation and existing tests to identify the termination path; done means the program exits cleanly without raising EOFError.
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