Make WSGIRequestHandler easier to be customized by the user
Open
Nobody has claimed this yet.
3.7 (EOL)
3.8 (EOL)
3.9 (EOL)
stdlib
type-feature
- Dominant language
- Python
- Stars
- 77.2k
- Forks
- 36k
- PR merge metrics
- PR metrics pending
Description
| BPO | 40700 |
|---|---|
| Nosy | @Zheaoli |
| 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 2020-05-20.15:54:01.331>
labels = ['3.7', '3.8', 'type-feature', 'library', '3.9']
title = 'Make WSGIRequestHandler easier to be customized by the user'
updated_at = <Date 2020-05-28.15:09:56.874>
user = 'https://github.com/Zheaoli'
bugs.python.org fields:
activity = <Date 2020-05-28.15:09:56.874>
actor = 'Manjusaka'
assignee = 'none'
closed = False
closed_date = None
closer = None
components = ['Library (Lib)']
creation = <Date 2020-05-20.15:54:01.331>
creator = 'Manjusaka'
dependencies = []
files = []
hgrepos = []
issue_num = 40700
keywords = ['patch']
message_count = 2.0
messages = ['369465', '370224']
nosy_count = 1.0
nosy_names = ['Manjusaka']
pr_nums = ['20262']
priority = 'normal'
resolution = None
stage = 'patch review'
status = 'open'
superseder = None
type = 'enhancement'
url = 'https://bugs.python.org/issue40700'
versions = ['Python 3.6', 'Python 3.7', '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
The issue names WSGIRequestHandler but no source file or tests. Start by reviewing linked PR #20262 and locating the WSGIRequestHandler entry point, then use the PR discussion to determine the intended customization surface. Done means the agreed customization change is implemented and covered by the relevant tests.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- python
- Domain
- backend
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100