Documenting all SO_* constants in socket module

Open
#57,096 3 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
2/5
Estimated time
1-3 hours
Newbie friendliness
25/100
Issue type
Documentation
Clarity
Mostly clear
Activity status
Stale
Tech stack
python
Domain
documentation

Research direction

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.

Written by the indexing model from the issue text.

Description

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

    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.