Missing mention of some class attributes in socketserver documentation
Nobody has claimed this yet.
Assessment
- Difficulty
- 2/5
- Estimated time
- 1-3 hours
- Newbie friendliness
- 25/100
- Issue type
- Documentation
- Clarity
- Needs clarification
- Activity status
- Stale
- Tech stack
- python
- Domain
- documentation
Research direction
Start with BPO issue 40057 and the socketserver documentation to identify which class attributes are missing from the reference. The issue lists pull request python/cpython#19147; completion would mean the relevant attributes are documented and the documentation changes are reviewed.
Written by the indexing model from the issue text.
Description
| BPO | 40057 |
|---|---|
| Nosy | @vadmium, @OverMighty |
| PRs |
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 2020-03-24.21:04:04.069>
labels = ['type-feature', '3.8', '3.9', '3.10', 'docs']
title = 'Missing mention of some class attributes in socketserver documentation'
updated_at = <Date 2020-05-23.20:09:52.790>
user = 'https://github.com/OverMighty'
bugs.python.org fields:
activity = <Date 2020-05-23.20:09:52.790>
actor = 'cheryl.sabella'
assignee = 'docs@python'
closed = False
closed_date = None
closer = None
components = ['Documentation']
creation = <Date 2020-03-24.21:04:04.069>
creator = 'overmighty'
dependencies = []
files = []
hgrepos = []
issue_num = 40057
keywords = ['patch']
message_count = 1.0
messages = ['364962']
nosy_count = 3.0
nosy_names = ['docs@python', 'martin.panter', 'overmighty']
pr_nums = ['19147']
priority = 'normal'
resolution = None
stage = 'patch review'
status = 'open'
superseder = None
type = 'enhancement'
url = 'https://bugs.python.org/issue40057'
versions = ['Python 3.8', 'Python 3.9', 'Python 3.10']
- Dominant language
- Python
- Stars
- 77.2k
- Forks
- 36k
- Avg merge
- 1d 9h
- Merged PRs (30d)
- 558
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.
More from python/cpython
-
docs pending
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
-
stdlib type-feature
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
-
stdlib type-feature
Difficulty 2/5 1-3 hours Newbie friendliness 72/100
-
build type-bug
Difficulty 2/5 1-3 hours Newbie friendliness 76/100
-
stdlib topic-email type-feature
Difficulty 2/5 1-3 hours Newbie friendliness 70/100
Similar issues
-
Difficulty 2/5 1-3 hours Newbie friendliness 82/100
-
Difficulty 2/5 1-3 hours Newbie friendliness 84/100
-
Difficulty 2/5 1-3 hours Newbie friendliness 68/100
-
Difficulty 2/5 1-3 hours Newbie friendliness 86/100
-
🐛 Bug 🔔 Pending processing
Difficulty 2/5 1-3 hours Newbie friendliness 84/100
jumpserver/jumpserver#17584 ·