-
Notifications
You must be signed in to change notification settings - Fork 1.4k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
DEP: Drop support for Python 3.8 #3051
Comments
Do you know if there has been such a "quick" support drop on the previous version ? |
The last time, both Python 3.6 and 3.7 where deprecated together on 2023-08-17. Python 3.7 went EOL on 2023-06-27. (Source: https://github.blog/changelog/2023-08-02-deprecation-notice-dependabot-to-drop-support-for-python-3-6-and-3-7/) |
.github/workflows/github-ci.yaml:
Could move this to 3.13, not 3.9? Would only really effect the "pycryptodome" case, since the "none" case is a subset of the standard "cryptography" cases. Advantages are forward looking and maybe (???) faster. |
I do not get this. Could you please elaborate? For moving this to Python 3.13: I do not think that this has substantial benefits for now. Speed should not really matter here, especially since I have seen Python 3.13 having a rather negative impact on the speed of some code (although not necessarily in our cases). |
Python 3.8 is EOL since 2024-10-07, id est for about three months. On 2025-02-05, Dependabot might stop updating critical pinned dependencies as per https://github.blog/changelog/2025-01-06-closing-down-notice-dependabot-will-no-longer-support-python-version-3-8/:
In the past, we usually supported EOL Python versions for about one further year, although we have no strong policy for this. (To match the corresponding Ubuntu release cycle, we would have to wait until April 2025 when Ubuntu 20.04 shipping Python 3.8 is going EOL for example.)
The text was updated successfully, but these errors were encountered: