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 — gh-138633: indicate SSL backend requirements for SSL functions by picnixz · Pull Request #138656 · python/cpython Conversation
|
|
@AA-Turner Do you mind reviewing this? or are you against a new extension (actually, do we encourage new Sphinx extensions or should we limit them?) |
Sorry, something went wrong.
There was an error while loading. Please reload this page.
This reverts commit 6df1740.
|
@AA-Turner I've removed the new directive as discussed. Please have a look for the rewording of the availability definition. |
Sorry, something went wrong.
There was an error while loading. Please reload this page.
8e294a6 to
df4f93b
Compare
|
Friendly ping @AA-Turner |
Sorry, something went wrong.
There was an error while loading. Please reload this page.
There was an error while loading. Please reload this page.
There was an error while loading. Please reload this page.
There was an error while loading. Please reload this page.
There was an error while loading. Please reload this page.
| was built. For instance, "Availability: OpenSSL >= 3.5" note means that the | ||
| feature is available if Python has been built with OpenSSL 3.5 or later, | ||
| while "Availability: not AWS-LC" note means that the feature is not available | ||
| if Python has been built with AWS-LC instead of OpenSSL. |
There was a problem hiding this comment.
The reason will be displayed to describe this comment to others. Learn more.
Should we imply a default of OpenSSL here?
Sorry, something went wrong.
There was an error while loading. Please reload this page.
There was a problem hiding this comment.
The reason will be displayed to describe this comment to others. Learn more.
I'd say "it depends". For now, we only have OpenSSL and AWS-LC that are "supported" and tested. We don't test LibreSSL or BoringSSL. In the future "not AWS-LC" may mean "everything that is libssl-like except AWS-LC". But this may be a bit annoying to actually say that "libssl-like" means. So, I don't have a preference. I think we should always assume that it should work with OpenSSL (maybe not with all its versions).
Sorry, something went wrong.
There was an error while loading. Please reload this page.
|
When you're done making the requested changes, leave the comment: |
Sorry, something went wrong.
There was an error while loading. Please reload this page.
Co-authored-by: Adam Turner <[email protected]>
|
I think I found a compromise. I tried to be as generic as possible in the introduction for the availability note, and a bit more precise in the SSL document itself. I have made the requested changes; please review again. |
Sorry, something went wrong.
There was an error while loading. Please reload this page.
|
Thanks for making the requested changes! @AA-Turner: please review the changes made to this pull request. |
Sorry, something went wrong.
There was an error while loading. Please reload this page.
There was an error while loading. Please reload this page.
|
@AA-Turner friendly ping |
Sorry, something went wrong.
There was an error while loading. Please reload this page.
|
This PR is stale because it has been open for 30 days with no activity. |
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.