urllib.parse.*Result: support _replace for additional computed addresses
Open
Nobody has claimed this yet.
3.8 (EOL)
stdlib
type-feature
- Dominant language
- Python
- Stars
- 77.2k
- Forks
- 36k
- Avg merge
- 1d 9h
- Merged PRs (30d)
- 558
Description
| BPO | 36418 |
|---|---|
| Nosy | @freddrake, @csabella |
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 2019-03-24.22:05:29.911>
labels = ['3.8', 'type-feature', 'library']
title = 'urllib.parse.*Result: support _replace for additional computed addresses'
updated_at = <Date 2019-03-27.13:46:03.747>
user = 'https://github.com/csabella'
bugs.python.org fields:
activity = <Date 2019-03-27.13:46:03.747>
actor = 'fdrake'
assignee = 'none'
closed = False
closed_date = None
closer = None
components = ['Library (Lib)']
creation = <Date 2019-03-24.22:05:29.911>
creator = 'cheryl.sabella'
dependencies = []
files = []
hgrepos = []
issue_num = 36418
keywords = []
message_count = 1.0
messages = ['338762']
nosy_count = 2.0
nosy_names = ['fdrake', 'cheryl.sabella']
pr_nums = []
priority = 'normal'
resolution = None
stage = None
status = 'open'
superseder = None
type = 'enhancement'
url = 'https://bugs.python.org/issue36418'
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
Start by locating the urllib.parse.*Result entry points and reviewing how _replace currently handles computed addresses. Clarify which additional addresses are in scope, then verify that the requested replacements are covered by tests and that the resulting values match the intended behavior.
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