Broken code for handling file://host in urllib.request.FileHandler.file_open
Nobody has claimed this yet.
Assessment
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Newbie friendliness
- 35/100
- Issue type
- Bug
- Clarity
- Needs clarification
- Activity status
- Stale
- Tech stack
- python
- Domain
- networking
Research direction
Start at urllib.request.FileHandler.file_open and review the file-handler.patch referenced in the issue. Determine the expected behavior for file://host URLs, then verify that the resulting handling matches that behavior and addresses the reported breakage.
Written by the indexing model from the issue text.
Description
| BPO | 21970 |
|---|---|
| Nosy | @orsenthil, @bitdancer, @vadmium, @mthuurne |
| 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 2014-07-13.01:49:21.025>
labels = ['3.7', 'type-bug', 'library']
title = 'Broken code for handling file://host in urllib.request.FileHandler.file_open'
updated_at = <Date 2019-10-07.14:21:55.816>
user = 'https://github.com/vadmium'
bugs.python.org fields:
activity = <Date 2019-10-07.14:21:55.816>
actor = 'mthuurne'
assignee = 'none'
closed = False
closed_date = None
closer = None
components = ['Library (Lib)']
creation = <Date 2014-07-13.01:49:21.025>
creator = 'martin.panter'
dependencies = []
files = ['39513']
hgrepos = []
issue_num = 21970
keywords = ['patch']
message_count = 6.0
messages = ['222901', '223095', '223634', '223636', '244144', '354100']
nosy_count = 5.0
nosy_names = ['orsenthil', 'r.david.murray', 'python-dev', 'martin.panter', 'mthuurne']
pr_nums = []
priority = 'normal'
resolution = None
stage = 'patch review'
status = 'open'
superseder = None
type = 'behavior'
url = 'https://bugs.python.org/issue21970'
versions = ['Python 3.4', 'Python 3.5', 'Python 3.6', 'Python 3.7']
- 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
-
Difficulty 2/5 1-3 hours Newbie friendliness 74/100
bancolombia/sentinel#23 ·
-
test md OpenCI
Difficulty 2/5 1-3 hours Newbie friendliness 74/100
-
integration:quickjs org:external priority:backlog topic:code-interpreter topic:middleware type:feature
Difficulty 2/5 1-3 hours Newbie friendliness 74/100
langchain-ai/deepagents#6450 ·
-
bug client
Difficulty 2/5 1-3 hours Newbie friendliness 88/100
-
Difficulty 2/5 1-3 hours Newbie friendliness 74/100