OpenSSL 1.1.0 deprecated functions

Open
#74,194 15 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
4/5
Estimated time
3-5 days
Newbie friendliness
20/100
Issue type
Bug
Clarity
Needs clarification
Activity status
Stale
Tech stack
python
Domain
build-system

Research direction

Start by reading build.log and the versioned OpenSSL patches listed in the issue, then compare the referenced pull requests to determine what remains unresolved. Done means the deprecated-function compatibility work is complete for the affected Python versions and the relevant builds succeed.

Written by the indexing model from the issue text.

Description

3.10 3.8 (EOL) 3.9 (EOL) build stdlib topic-SSL
BPO 30008
Nosy @tiran, @alex, @floppym, @dstufft, @csabella, @markwright, @miss-islington
PRs
  • python/cpython#3934
  • python/cpython#3943
  • python/cpython#20397
  • python/cpython#20565
  • python/cpython#20566
  • python/cpython#20567
    		•
    Files
  • build.log: build log
  • python-2.7.14-openssl-1.1.0.patch: python-2.7.14-openssl-1.1.0.patch
  • python-3.4.6-openssl-1.1.0.patch: python-3.4.6-openssl-1.1.0.patch
  • python-3.5.4-openssl-1.1.0.patch: python-3.5.4-openssl-1.1.0.patch
  • python-3.6.3-openssl-1.1.0.patch: python-3.6.3-openssl-1.1.0.patch
    		•

    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-04-06.16:34:45.622>
labels = ['3.8', 'build', 'library', '3.9', '3.10']
title = 'OpenSSL 1.1.0 deprecated functions'
updated_at = <Date 2020-06-01.07:18:42.523>
user = 'https://github.com/floppym'

    bugs.python.org fields:

    activity = <Date 2020-06-01.07:18:42.523>
actor = 'miss-islington'
assignee = 'none'
closed = False
closed_date = None
closer = None
components = ['Library (Lib)']
creation = <Date 2017-04-06.16:34:45.622>
creator = 'floppymaster'
dependencies = []
files = ['46782', '47198', '47199', '47200', '47201']
hgrepos = []
issue_num = 30008
keywords = ['patch']
message_count = 15.0
messages = ['291236', '291343', '291345', '303951', '303953', '303954', '303955', '303967', '304028', '369904', '369906', '370535', '370536', '370537', '370538']
nosy_count = 10.0
nosy_names = ['janssen', 'christian.heimes', 'Arfrever', 'alex', 'devurandom', 'floppymaster', 'dstufft', 'cheryl.sabella', 'gienah', 'miss-islington']
pr_nums = ['3934', '3943', '20397', '20565', '20566', '20567']
priority = 'normal'
resolution = None
stage = 'patch review'
status = 'open'
superseder = None
type = 'compile error'
url = 'https://bugs.python.org/issue30008'
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

    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.