Add warnings to ssl.PROTOCOL_TLSv1 and ssl.PROTOCOL_TLSv1_1 docs

Open
#87,806 1 comment 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
1/5
Estimated time
Under an hour
Newbie friendliness
35/100
Issue type
Documentation
Clarity
Mostly clear
Activity status
Stale
Tech stack
python
Domain
documentation

Research direction

Review the existing python/cpython#25040 pull request and the documentation for ssl.PROTOCOL_TLSv1 and ssl.PROTOCOL_TLSv1_1. Confirm the intended warning wording and whether both protocol entries are covered; the documentation is done when each entry clearly warns about its status.

Written by the indexing model from the issue text.

Description

3.10 docs type-feature
BPO 43640
Nosy @illia-v
PRs
  • python/cpython#25040
    		•

    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-03-27.15:40:09.964>
labels = ['type-feature', '3.10', 'docs']
title = 'Add warnings to ssl.PROTOCOL_TLSv1 and ssl.PROTOCOL_TLSv1_1 docs'
updated_at = <Date 2021-03-27.15:44:10.694>
user = 'https://github.com/illia-v'

    bugs.python.org fields:

    activity = <Date 2021-03-27.15:44:10.694>
actor = 'illia-v'
assignee = 'docs@python'
closed = False
closed_date = None
closer = None
components = ['Documentation']
creation = <Date 2021-03-27.15:40:09.964>
creator = 'illia-v'
dependencies = []
files = []
hgrepos = []
issue_num = 43640
keywords = ['patch']
message_count = 1.0
messages = ['389606']
nosy_count = 2.0
nosy_names = ['docs@python', 'illia-v']
pr_nums = ['25040']
priority = 'normal'
resolution = None
stage = 'patch review'
status = 'open'
superseder = None
type = 'enhancement'
url = 'https://bugs.python.org/issue43640'
versions = ['Python 3.10']

    Dominant language
    Python
    Stars
    77.2k
    Forks
    36k
    Avg merge
    1d 9h
    Merged PRs (30d)
    558

    Contributor guide

    Open the contributing guide

    First steps

    1. Read the whole issue, then the project's contributing guide.
    2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
    3. Fork the repository and make your change on a branch.
    4. Open a pull request that references the issue number.

    More from python/cpython

    All issues in python/cpython

    Similar issues

    More Python issues

    Get new issues in your inbox

    A short digest of beginner-friendly GitHub issues.