GeezerVisonThe World Wide Web, restored to 800 pixels of glory. | |||||||
| Home|About|Gaming cabinet|Archives|How it works|Starter sites | |||||||
GeezerVison is showing github.com — [3.14] gh-148292: Add OpenSSL 4 support by vstinner · Pull Request #149783 · python/cpython Conversation
|
|
Can we wait a bit before doing so? I do not want to fix openssl issues arising in a bugfix because we added support for OSSL4. It is a major change and for instance, I did not backport the use of the EVP API introduced in 3.x for HMAC to older releases. I really want to wait for users to test 3.15 with 4.0, say until aftrr 3.15.1, and we can add it to 3.14 afterwards. It would not help backports though as each version has its own ssl.c (almost) |
Sorry, something went wrong.
There was an error while loading. Please reload this page.
|
Ok, in this case, I prefer closing my PR. For my own workflow, I prefer to not keep PRs opens for too long. The PR can be reopened/recreated later. |
Sorry, something went wrong.
There was an error while loading. Please reload this page.
|
@vstinner We have applied this backport downstream in Pyenv so that users can link against OpenSSL 4 if they wish / if it's the default on their system. Is it reasonable to expect that if there are further OpenSSL 4 -- related fixes before the official backport, they will be added to this PR? |
Sorry, something went wrong.
There was an error while loading. Please reload this page.
|
We can revisit (reopen) this PR later. If this PR is reopened, we will add further changes if there are more OpenSSL 4.0 changes. @picnixz would like to wait for user feedback testing Python 3.15 with OpenSSL 4.0. |
Sorry, something went wrong.
There was an error while loading. Please reload this page.
|
Yes I want to wait at least until 3.15.0 is out and we can reconsider this in 3.15.1. |
Sorry, something went wrong.
There was an error while loading. Please reload this page.
There was an error while loading. Please reload this page.
|
Could this one be reconsidered now please? OpenSSL 3.6.x is EOL, so people are stuck on 3.5.x or >=4.x now. 3.15 seems okay for me except for: |
Sorry, something went wrong.
There was an error while loading. Please reload this page.
Wow, I thought 3.6 was the LTS and not 3.5 (I think I was biased bc of Python 3.6 which lasted longer in many distros compared to 3.5). I don't think being "stuck" in 3.5 is a problem though (but I may once again have mixed the supported features). That being said, let's first fix the 4.x support in 3.15+ before backporting anything, indeed. |
Sorry, something went wrong.
There was an error while loading. Please reload this page.
There was an error while loading. Please reload this page.
Successfully merging this pull request may close these issues.
There was an error while loading. Please reload this page.