List socket.SO_*, SCM_*, MSG_*, IPPROTO_* symbols
Open
Nobody has claimed this yet.
docs
topic-socket
type-feature
- Dominant language
- Python
- Stars
- 77.2k
- Forks
- 36k
- PR merge metrics
- PR metrics pending
Description
| BPO | 27409 |
|---|---|
| Nosy | @giampaolo, @vadmium |
| Files |
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-29.02:54:56.890>
labels = ['docs']
title = 'List socket.SO_*, SCM_*, MSG_*, IPPROTO_* symbols'
updated_at = <Date 2019-05-03.16:44:31.642>
user = 'https://github.com/vadmium'
bugs.python.org fields:
activity = <Date 2019-05-03.16:44:31.642>
actor = 'zach.ware'
assignee = 'docs@python'
closed = False
closed_date = None
closer = None
components = ['Documentation']
creation = <Date 2016-06-29.02:54:56.890>
creator = 'martin.panter'
dependencies = []
files = ['43573']
hgrepos = []
issue_num = 27409
keywords = ['patch']
message_count = 1.0
messages = ['269460']
nosy_count = 4.0
nosy_names = ['giampaolo.rodola', 'docs@python', 'martin.panter', 'Martha Simons']
pr_nums = []
priority = 'normal'
resolution = None
stage = 'patch review'
status = 'open'
superseder = None
type = None
url = 'https://bugs.python.org/issue27409'
versions = ['Python 3.5', 'Python 3.6']
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by reviewing the linked socket-const.patch and the BPO issue 27409, which contain the existing work and context. Locate the CPython documentation entry for socket constants, then verify that the SO_, SCM_, MSG_, and IPPROTO_ symbols requested by the issue are listed consistently and that the documentation build passes.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- python
- Domain
- documentation
- Issue type
- Documentation
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100