tempfile.TemporaryFile: name of file descriptor cannot be reused in consecutive initialization
Open
Nobody has claimed this yet.
3.8 (EOL)
3.9 (EOL)
stdlib
type-bug
- Dominant language
- Python
- Stars
- 77.2k
- Forks
- 36k
- PR merge metrics
- PR metrics pending
Description
| BPO | 44013 |
|---|---|
| Nosy | @tjol, @zhongxiang117 |
| 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 2021-05-02.22:33:35.276>
labels = ['3.8', 'type-bug', 'library', '3.9']
title = 'tempfile.TemporaryFile: name of file descriptor cannot be reused in consecutive initialization'
updated_at = <Date 2021-06-07.22:11:27.108>
user = 'https://github.com/zhongxiang117'
bugs.python.org fields:
activity = <Date 2021-06-07.22:11:27.108>
actor = 'zhongxiang117'
assignee = 'none'
closed = False
closed_date = None
closer = None
components = ['Library (Lib)']
creation = <Date 2021-05-02.22:33:35.276>
creator = 'zhongxiang117'
dependencies = []
files = ['50004', '50093']
hgrepos = []
issue_num = 44013
keywords = []
message_count = 5.0
messages = ['392746', '395089', '395154', '395156', '395291']
nosy_count = 2.0
nosy_names = ['tjollans', 'zhongxiang117']
pr_nums = []
priority = 'normal'
resolution = 'wont fix'
stage = None
status = 'open'
superseder = None
type = 'behavior'
url = 'https://bugs.python.org/issue44013'
versions = ['Python 3.8', 'Python 3.9']
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 reproduction code in xtempfile.py and new-xtempfile.py, then trace the affected TemporaryFile behavior in the tempfile library. The issue provides no accepted fix or completion criterion, and its historical resolution is "wont fix," so confirm the current behavior before proposing any change.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- python
- Domain
- operating-systems
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100