Make urllib.parse.SplitResult etc arguments optional

未关闭
#67,604 4 条评论 0 个 reaction 已指派 0 人 在 GitHub 查看

还没有人认领这个 Issue。

评估

难度
3/5
预计耗时
1-2 天
新手友好度
35/100
Issue 类型
功能
描述清晰度
基本清楚
活跃度
停滞
技术栈
python
领域
backend

调研方向

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.

由索引模型根据 Issue 内容生成。

描述

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']
    

    主要语言
    Python
    星标
    77.2k
    派生
    36k
    平均合并
    1 天 9 小时
    30 天内合并 PR
    558

    贡献指南

    打开贡献指南

    从这里开始

    1. 先读完整个 Issue,再读项目的贡献指南。
    2. 在 Issue 下留言说明你要接手 —— 这能避免两个人做同样的事。
    3. Fork 仓库,在一个分支上完成修改。
    4. 提交 Pull Request,并在描述里引用这个 Issue 编号。

    python/cpython 的其他 Issue

    查看 python/cpython 的全部 Issue

    相似的 Issue

    更多 Python Issue

    把新 issue 发到你的邮箱

    精选适合新手参与的 GitHub issue 摘要。