-
-
Notifications
You must be signed in to change notification settings - Fork 507
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
Drop python 3.6 before we start 3.10 migration #1947
Comments
It also doesn't support OpenSSL 3.0.0 so I'm in favour of dropping it as well to make that simplier 👍 |
Even though it's not EOL yet, this would still mean dropping it much later in the life cycle than 3.5: #127 was exactly 3 years ago (and release cadence between 3.5 & 3.6 was 18 month; 3.5.10 final was September 5, 2020) |
@h-vetinari to preserve CI resources we decided to follow nep 29. According to that we should have dropped 3.6 a while back already. |
I'm in favor of remaining at only 6 python versions (3.7, 3.8, 3.9, 3.10, and the two pypy versions). |
Given that we will be dropping py36 should we also drop pypy36 ? |
No need to convince me. ;-) |
I would say yes, especially as pypy3.8 is in the relatively near future; CC @mattip |
Dropping pypy3.6 is fine |
pypy3.6 was dropped months ago. |
We didn't decide to do this AFAIK. |
I believe we did decide but we never implemented it b/c many folks still needed Python 3.6 for a while longer. I guess we stayed on the fence on that one. |
Can this issue be closed now that #1955 is merged and the website has been updated in conda-forge/conda-forge.github.io#1516? Or is additional work needed? |
Yes, thanks.
Yeah, the NEP was one but not the only consideration we had :). Things will get more interesting when we'll discuss (next year or so) when to drop 3.7 (when it's not just months but more than a year of time difference) :D |
Just wanted to bring up the question of whether there should be exceptions for security-relevant packages like |
3.6 is EOL in three months and I don't think we should make it part of the 3.10 migration.
@conda-forge/core, @conda-forge/python, thoughts?
The text was updated successfully, but these errors were encountered: