Do not add duplicate FDs to list in duplicate_for_child()
Open
Nobody has claimed this yet.
3.10
3.8 (EOL)
3.9 (EOL)
stdlib
type-bug
- Dominant language
- Python
- Stars
- 77.2k
- Forks
- 36k
- Avg merge
- 1d 9h
- Merged PRs (30d)
- 558
Description
| BPO | 43142 |
|---|---|
| Nosy | @terryjreedy, @pitrou, @applio, @imaginary-person |
| PRs |
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-02-06.05:50:31.148>
labels = ['3.8', 'type-bug', 'library', '3.9', '3.10']
title = 'Do not add duplicate FDs to list in duplicate_for_child()'
updated_at = <Date 2021-02-13.05:57:18.897>
user = 'https://github.com/imaginary-person'
bugs.python.org fields:
activity = <Date 2021-02-13.05:57:18.897>
actor = 'terry.reedy'
assignee = 'none'
closed = False
closed_date = None
closer = None
components = ['Library (Lib)']
creation = <Date 2021-02-06.05:50:31.148>
creator = 'sanchit'
dependencies = []
files = []
hgrepos = []
issue_num = 43142
keywords = ['patch']
message_count = 4.0
messages = ['386546', '386881', '386897', '386913']
nosy_count = 4.0
nosy_names = ['terry.reedy', 'pitrou', 'davin', 'sanchit']
pr_nums = ['24461']
priority = 'normal'
resolution = None
stage = 'patch review'
status = 'open'
superseder = None
type = 'behavior'
url = 'https://bugs.python.org/issue43142'
versions = ['Python 3.8', 'Python 3.9', 'Python 3.10']
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 reviewing the duplicate_for_child() entry point and the referenced PR 24461, since the issue provides no file or test path. Confirm that duplicate file descriptors are not added more than once, then use the existing PR context to identify the relevant regression coverage and expected behavior.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- python
- Domain
- operating-systems
- Issue type
- Bug
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 25/100