Make urllib.parse.SplitResult etc arguments optional

Open
#67,604 4 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
3/5
Estimated time
1-2 days
Newbie friendliness
35/100
Issue type
Feature
Clarity
Mostly clear
Activity status
Stale
Tech stack
python
Domain
backend

Research direction

Start by inspecting the urllib.parse result classes named in the issue and reviewing the linked historical split-result-default.patch. Check the existing urllib.parse tests and verify that the affected SplitResult variants accept omitted arguments with the intended defaults.

Written by the indexing model from the issue text.

Description

stdlib type-feature
BPO 23416
Nosy @rhettinger, @vadmium, @serhiy-storchaka
Files
  • split-result-default.patch
    		•

    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 2015-02-09.04:03:57.933>
labels = ['type-feature', 'library']
title = 'Make urllib.parse.SplitResult etc arguments optional'
updated_at = <Date 2015-12-08.09:08:05.958>
user = 'https://github.com/vadmium'

    bugs.python.org fields:

    activity = <Date 2015-12-08.09:08:05.958>
actor = 'serhiy.storchaka'
assignee = 'none'
closed = False
closed_date = None
closer = None
components = ['Library (Lib)']
creation = <Date 2015-02-09.04:03:57.933>
creator = 'martin.panter'
dependencies = []
files = ['38076']
hgrepos = []
issue_num = 23416
keywords = ['patch']
message_count = 3.0
messages = ['235584', '235664', '256104']
nosy_count = 3.0
nosy_names = ['rhettinger', 'martin.panter', 'serhiy.storchaka']
pr_nums = []
priority = 'normal'
resolution = None
stage = None
status = 'open'
superseder = None
type = 'enhancement'
url = 'https://bugs.python.org/issue23416'
versions = ['Python 3.5']

    Dominant language
    Python
    Stars
    77.2k
    Forks
    36k
    Avg merge
    1d 9h
    Merged PRs (30d)
    558

    Contributor guide

    Open the contributing guide

    First steps

    1. Read the whole issue, then the project's contributing guide.
    2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
    3. Fork the repository and make your change on a branch.
    4. Open a pull request that references the issue number.

    More from python/cpython

    All issues in python/cpython

    Similar issues

    More Python issues

    Get new issues in your inbox

    A short digest of beginner-friendly GitHub issues.