Case of headers in urllib.request.Request
Open
Nobody has claimed this yet.
stdlib
type-bug
- Dominant language
- Python
- Stars
- 77.2k
- Forks
- 36k
- Avg merge
- 1d 9h
- Merged PRs (30d)
- 558
Description
| BPO | 45145 |
|---|---|
| Nosy | @emphoeller |
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-09-09.00:39:40.871>
labels = ['type-bug', 'library']
title = 'Case of headers in urllib.request.Request'
updated_at = <Date 2021-09-09.00:39:40.871>
user = 'https://github.com/emphoeller'
bugs.python.org fields:
activity = <Date 2021-09-09.00:39:40.871>
actor = 'emphoeller'
assignee = 'none'
closed = False
closed_date = None
closer = None
components = ['Library (Lib)']
creation = <Date 2021-09-09.00:39:40.871>
creator = 'emphoeller'
dependencies = []
files = []
hgrepos = []
issue_num = 45145
keywords = []
message_count = 1.0
messages = ['401429']
nosy_count = 1.0
nosy_names = ['emphoeller']
pr_nums = []
priority = 'normal'
resolution = None
stage = None
status = 'open'
superseder = None
type = 'behavior'
url = 'https://bugs.python.org/issue45145'
versions = []
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
The issue identifies urllib.request.Request but does not name a source file, test, or expected behavior beyond header casing. Start by locating the Request implementation and its existing tests, then determine the intended case handling from the surrounding behavior and issue history. Done requires a reproducible behavior and a corresponding regression test, but the payload does not define the expected result.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- python
- Domain
- networking
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 20/100