ssl deprecation warnings erganomics
Open
Nobody has claimed this yet.
3.10
3.11
topic-SSL
type-bug
- Dominant language
- Python
- Stars
- 77.2k
- Forks
- 36k
- PR merge metrics
- PR metrics pending
Description
| BPO | 44354 |
|---|---|
| Nosy | @alex, @graingert, @dstufft |
| 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 2021-06-08.20:36:09.894>
labels = ['expert-SSL', 'type-bug', '3.10', '3.11']
title = 'ssl deprecation warnings erganomics'
updated_at = <Date 2021-06-10.13:18:20.153>
user = 'https://github.com/graingert'
bugs.python.org fields:
activity = <Date 2021-06-10.13:18:20.153>
actor = 'christian.heimes'
assignee = 'none'
closed = False
closed_date = None
closer = None
components = ['SSL']
creation = <Date 2021-06-08.20:36:09.894>
creator = 'graingert'
dependencies = []
files = []
hgrepos = []
issue_num = 44354
keywords = []
message_count = 5.0
messages = ['395362', '395366', '395524', '395526', '395528']
nosy_count = 4.0
nosy_names = ['janssen', 'alex', 'graingert', 'dstufft']
pr_nums = ['26599']
priority = 'normal'
resolution = None
stage = 'needs patch'
status = 'open'
superseder = None
type = 'behavior'
url = 'https://bugs.python.org/issue44354'
versions = ['Python 3.10', 'Python 3.11']
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 reading the SSL component context and the existing pull request python/cpython#26599. The issue provides no file or test entry point, so use that PR to identify the affected deprecation warnings and expected ergonomics; done means the warnings behave as intended for Python 3.10 and 3.11.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- python
- Domain
- security
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 15/100