Documenting all SO_* constants in socket module

未关闭
#57,096 3 条评论 0 个 reaction 已指派 0 人 在 GitHub 查看

还没有人认领这个 Issue。

评估

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

调研方向

Review the socket module documentation and the existing PR #3072 first; the issue does not name a documentation file or test. The work is complete when all SO_* constants exposed by the socket module are documented, with the relevant documentation checks passing if available.

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

描述

docs topic-socket
BPO 12887
Nosy @ezio-melotti, @merwok, @sandrotosi, @vadmium
PRs
  • python/cpython#3072
  • 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 2011-09-02.18:12:59.894>
    labels = ['3.7', 'docs']
    title = 'Documenting all SO_* constants in socket module'
    updated_at = <Date 2017-08-22.23:34:26.116>
    user = 'https://github.com/sandrotosi'
    

    bugs.python.org fields:

    activity = <Date 2017-08-22.23:34:26.116>
    actor = 'Mariatta'
    assignee = 'docs@python'
    closed = False
    closed_date = None
    closer = None
    components = ['Documentation']
    creation = <Date 2011-09-02.18:12:59.894>
    creator = 'sandro.tosi'
    dependencies = []
    files = []
    hgrepos = []
    issue_num = 12887
    keywords = []
    message_count = 3.0
    messages = ['143428', '221494', '272495']
    nosy_count = 5.0
    nosy_names = ['ezio.melotti', 'eric.araujo', 'sandro.tosi', 'docs@python', 'martin.panter']
    pr_nums = ['3072']
    priority = 'normal'
    resolution = None
    stage = 'patch review'
    status = 'open'
    superseder = None
    type = None
    url = 'https://bugs.python.org/issue12887'
    versions = ['Python 3.6', 'Python 3.7']
    

    主要语言
    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 摘要。