Documentation of SSL library
Open
Nobody has claimed this yet.
3.7 (EOL)
3.8 (EOL)
3.9 (EOL)
docs
topic-SSL
type-feature
- Dominant language
- Python
- Stars
- 77.2k
- Forks
- 36k
- PR merge metrics
- PR metrics pending
Description
| BPO | 40127 |
|---|---|
| Nosy | @tiran, @christopheNan |
| 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-31.16:40:25.242>
labels = ['3.8', 'type-feature', '3.7', '3.9', 'docs']
title = 'Documentation of SSL library'
updated_at = <Date 2020-04-04.03:17:20.699>
user = 'https://github.com/christopheNan'
bugs.python.org fields:
activity = <Date 2020-04-04.03:17:20.699>
actor = 'terry.reedy'
assignee = 'docs@python'
closed = False
closed_date = None
closer = None
components = ['Documentation']
creation = <Date 2020-03-31.16:40:25.242>
creator = 'Christophe Nanteuil'
dependencies = []
files = []
hgrepos = []
issue_num = 40127
keywords = ['patch']
message_count = 4.0
messages = ['365398', '365402', '365408', '365615']
nosy_count = 3.0
nosy_names = ['christian.heimes', 'docs@python', 'Christophe Nanteuil']
pr_nums = ['19253']
priority = 'normal'
resolution = None
stage = 'patch review'
status = 'open'
superseder = None
type = 'enhancement'
url = 'https://bugs.python.org/issue40127'
versions = ['Python 3.7', 'Python 3.8', 'Python 3.9']
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 existing python/cpython#19253 pull request and the Documentation component details for BPO issue 40127. The issue does not name files or a specific documentation gap; completion would mean the SSL library documentation requested by that issue is addressed and the existing patch work is resolved.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- python
- Domain
- documentation, security
- Issue type
- Documentation
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 20/100