urlparse doesn't validate the scheme
Open
Nobody has claimed this yet.
3.8 (EOL)
stdlib
type-bug
- Dominant language
- Python
- Stars
- 77.2k
- Forks
- 36k
- PR merge metrics
- PR metrics pending
Description
| BPO | 35377 |
|---|---|
| Nosy | @orsenthil, @stevendaprano |
| 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 2018-12-02.15:27:37.514>
labels = ['3.8', 'type-bug', 'library']
title = "urlparse doesn't validate the scheme"
updated_at = <Date 2018-12-03.22:51:57.402>
user = 'https://bugs.python.org/devkral'
bugs.python.org fields:
activity = <Date 2018-12-03.22:51:57.402>
actor = 'steven.daprano'
assignee = 'none'
closed = False
closed_date = None
closer = None
components = ['Library (Lib)']
creation = <Date 2018-12-02.15:27:37.514>
creator = 'devkral'
dependencies = []
files = []
hgrepos = []
issue_num = 35377
keywords = []
message_count = 8.0
messages = ['330884', '330886', '330888', '330904', '330927', '330938', '330976', '330993']
nosy_count = 4.0
nosy_names = ['orsenthil', 'steven.daprano', 'SilentGhost', 'devkral']
pr_nums = ['10862']
priority = 'normal'
resolution = None
stage = None
status = 'open'
superseder = None
type = 'behavior'
url = 'https://bugs.python.org/issue35377'
versions = ['Python 3.8']
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 concerns urlparse in Python's Library (Lib) component, but names no file or test. Review PR #10862 first, then locate the urlparse implementation and its tests; done means the scheme is validated as requested by the issue title.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- python
- Domain
- backend
- Issue type
- Bug
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100