Catch FileNotFoundError in socketserver.DatagramRequestHandler
Nobody has claimed this yet.
Assessment
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Newbie friendliness
- 45/100
- Issue type
- Bug
- Clarity
- Mostly clear
- Activity status
- Quiet
- Tech stack
- python
- Domain
- networking
Research direction
Start with the socketserver.DatagramRequestHandler entry point and use server_dgram.py to reproduce the Unix Domain socket datagram case. Compare the existing issue26403.patch and issue26403_v2.patch, then run the relevant socketserver tests or reproduction. Done means the missing-file condition is handled as described without breaking the handler's normal behavior.
Written by the indexing model from the issue text.
Description
| BPO | 26403 |
|---|---|
| Nosy | @berkerpeksag, @vadmium, @desbma |
| 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 2016-02-21.19:28:45.686>
labels = ['type-bug', 'library', '3.10']
title = 'Catch FileNotFoundError in socketserver.DatagramRequestHandler'
updated_at = <Date 2021-03-22.16:28:50.849>
user = 'https://github.com/desbma'
bugs.python.org fields:
activity = <Date 2021-03-22.16:28:50.849>
actor = 'iritkatriel'
assignee = 'none'
closed = False
closed_date = None
closer = None
components = ['Library (Lib)']
creation = <Date 2016-02-21.19:28:45.686>
creator = 'desbma'
dependencies = []
files = ['41990', '41991', '42009']
hgrepos = []
issue_num = 26403
keywords = ['patch']
message_count = 5.0
messages = ['260632', '260648', '260649', '260665', '260699']
nosy_count = 3.0
nosy_names = ['berker.peksag', 'martin.panter', 'desbma']
pr_nums = []
priority = 'normal'
resolution = None
stage = None
status = 'open'
superseder = None
type = 'behavior'
url = 'https://bugs.python.org/issue26403'
versions = ['Python 3.10']
- Dominant language
- Python
- Stars
- 77.2k
- Forks
- 36k
- Avg merge
- 1d 9h
- Merged PRs (30d)
- 558
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.
More from python/cpython
-
docs pending
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
-
stdlib type-feature
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
-
stdlib type-feature
Difficulty 2/5 1-3 hours Newbie friendliness 72/100
-
build type-bug
Difficulty 2/5 1-3 hours Newbie friendliness 76/100
-
stdlib topic-email type-feature
Difficulty 2/5 1-3 hours Newbie friendliness 70/100
Similar issues
-
🐛 Bug 🔔 Pending processing
Difficulty 2/5 1-3 hours Newbie friendliness 84/100
jumpserver/jumpserver#17584 ·
-
link-check link-check:sphinx-theme
Difficulty 2/5 1-3 hours Newbie friendliness 72/100
-
Difficulty 2/5 1-3 hours Newbie friendliness 90/100
modelscope/DiffSynth-Studio#1702 ·
-
Difficulty 2/5 1-3 hours Newbie friendliness 65/100
qgis/QGIS-Documentation#11275 ·
-
bug priority:normal ready-for-dev
Difficulty 2/5 1-3 hours Newbie friendliness 88/100
OpenHands/extensions#626 · 1 comment ·