Conversation
Drop unneeded code.
|
Looking at PyPI stats we've currently still got fairly significant 3.9 usage. Perhaps a smart approach here would be...
(Alternatively we could be more pushy about this with our userbase. 2025-10 seems like a long time to wait for this.) |
|
Maybe it could be done based on python version? |
|
@Secrus - Could phase it in gradually yep. Or eg... support it in Python 3.14. |
|
I would be uncomfortable dropping support for Python 3.9 before EOL, but it is worth noting there are other ecosystem packages that do this, e.g., |
|
Maybe I am missing something, but according to some experiences made with SSL module of python 3.8 on Windows, see: https://github.com/python/cpython/blob/39b2f82717a69dde7212bc39b673b0f55c99e6a3/Lib/ssl.py#L750 As of python 3.8 ssl module also performs host name verification by default. So why struggle with custom cert store libraries? |
|
@deathaxe Behavior of the stdlib |
|
I suggest adding Python 3.14 to the test suite as in: |
| strategy: | ||
| matrix: | ||
| python-version: ["3.8", "3.9", "3.10", "3.11", "3.12"] | ||
| python-version: ["3.10", "3.11", "3.12", "3.13"] |
There was a problem hiding this comment.
| python-version: ["3.10", "3.11", "3.12", "3.13"] | |
| python-version: ["3.10", "3.11", "3.12", "3.13", "3.14"] |
|
Support for Python 3.9 ended more than 3 month ago. I don't see a hold-up anymore or? Any help required? |
Refs #302.
Switch from
certifitotruststorein order to enable system trust stores as our default SSL behavior. Related… #3404 (comment)Requires us to bump our Python requirement from 3.8 to 3.10.