Add getters for all SSLContext internal configuration
Open
Nobody has claimed this yet.
3.8 (EOL)
topic-SSL
type-feature
- Dominant language
- Python
- Stars
- 77.2k
- Forks
- 36k
- PR merge metrics
- PR metrics pending
Description
| BPO | 32359 |
|---|---|
| Nosy | @tiran, @alex, @njsmith, @dstufft |
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 2017-12-18.09:41:45.683>
labels = ['expert-SSL', 'type-feature', '3.8']
title = 'Add getters for all SSLContext internal configuration'
updated_at = <Date 2018-02-26.08:33:36.485>
user = 'https://github.com/njsmith'
bugs.python.org fields:
activity = <Date 2018-02-26.08:33:36.485>
actor = 'christian.heimes'
assignee = 'none'
closed = False
closed_date = None
closer = None
components = ['SSL']
creation = <Date 2017-12-18.09:41:45.683>
creator = 'njs'
dependencies = []
files = []
hgrepos = []
issue_num = 32359
keywords = []
message_count = 8.0
messages = ['308533', '308535', '308536', '308541', '308547', '308548', '308594', '312890']
nosy_count = 5.0
nosy_names = ['janssen', 'christian.heimes', 'alex', 'njs', 'dstufft']
pr_nums = []
priority = 'normal'
resolution = None
stage = 'needs patch'
status = 'open'
superseder = None
type = 'enhancement'
url = 'https://bugs.python.org/issue32359'
versions = ['Python 3.8']
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 locating Python's SSLContext implementation and its existing tests, then review the SSL-specific issue context before deciding which internal configuration values need public getters. Done means the requested SSLContext configuration is exposed consistently and covered by tests, but the issue does not name specific files or values.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- python
- Domain
- security
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 30/100