This issue tracker has been migrated to GitHub, and is currently read-only.
For more information, see the GitHub FAQs in the Python's Developer Guide.

Author jakirkham
Recipients amacd31, christian.heimes, jakirkham, jan-xyz, methane, ronaldoussoren
Date 2021-06-02.21:35:28
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <1622669728.29.0.103409597998.issue42853@roundup.psfhosted.org>
In-reply-to
Content
Would it be possible to check for these newer OpenSSL symbols during the builds of Python 3.8 & 3.9 (using them when available and otherwise falling back to the older API otherwise)? This would allow people to build Python 3.8 & 3.9 with the newer OpenSSL benefiting from the fix

That said, not sure if there are other obstacles to using OpenSSL 1.1.1 with Python 3.8 & 3.9
History
Date User Action Args
2021-06-02 21:35:28jakirkhamsetrecipients: + jakirkham, ronaldoussoren, christian.heimes, methane, amacd31, jan-xyz
2021-06-02 21:35:28jakirkhamsetmessageid: <1622669728.29.0.103409597998.issue42853@roundup.psfhosted.org>
2021-06-02 21:35:28jakirkhamlinkissue42853 messages
2021-06-02 21:35:28jakirkhamcreate