python / python/cpython

Documentation corrections for email defects

未关闭
#71,515 2 条评论 0 个 reaction 已指派 0 人 在 GitHub 查看

还没有人认领这个 Issue。

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

描述

BPO 27328
Nosy @warsaw, @bitdancer, @vadmium
Dependencies
  • bpo-24364: Not all defects pass through email policy
  • Files
  • defect-doc.patch
  • defect-doc.v2.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 2016-06-16.04:36:20.590>
    labels = ['expert-email']
    title = 'Documentation corrections for email defects'
    updated_at = <Date 2016-06-20.08:49:57.078>
    user = 'https://github.com/vadmium'
    

    bugs.python.org fields:

    activity = <Date 2016-06-20.08:49:57.078>
    actor = 'martin.panter'
    assignee = 'none'
    closed = False
    closed_date = None
    closer = None
    components = ['email']
    creation = <Date 2016-06-16.04:36:20.590>
    creator = 'martin.panter'
    dependencies = ['24364']
    files = ['43404', '43482']
    hgrepos = []
    issue_num = 27328
    keywords = ['patch']
    message_count = 2.0
    messages = ['268640', '268887']
    nosy_count = 3.0
    nosy_names = ['barry', 'r.david.murray', 'martin.panter']
    pr_nums = []
    priority = 'normal'
    resolution = None
    stage = 'patch review'
    status = 'open'
    superseder = None
    type = None
    url = 'https://bugs.python.org/issue27328'
    versions = ['Python 3.5', 'Python 3.6']
    

    贡献指南

    打开贡献指南

    从这里开始

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

    调研方向

    先阅读 defect-doc.v2.patch,然后将其中提出的修正与电子邮件文档和依赖项 bpo-24364 进行比较。应用修正后运行文档检查;当文档所描述的 email-policy 行为与缺陷范围一致,并且文档构建通过时,即视为完成。

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

    评估

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

    把新 issue 发到你的邮箱

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