python
gh-138633: indicate SSL backend requirements for SSL functions
If we are going to support multiple flavors of libssl, we should also plan to ease our life in the future when we want to say "this is ok for this flavor" so I added a Sphinx extension (actually it's similar to the availability directive but I decided to have a separate directive as it's not really the same; since the code would be the same, I just made a base directive class for that)
- Issue: gh-138633
📚 Documentation preview 📚: https://cpython-previews--138656.org.readthedocs.build/
@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?)
@AA-Turner I've removed the new directive as discussed. Please have a look for the rewording of the availability definition.
When you're done making the requested changes, leave the comment: I have made the requested changes; please review again.
![bedevere-app[bot] avatar](https://avatars.githubusercontent.com/in/388350?v=4 "Published by a pub.dev verified publisher"){kind=small}
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.
Thanks for making the requested changes!
@AA-Turner: please review the changes made to this pull request.