-
Notifications
You must be signed in to change notification settings - Fork 1k
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.10 #6648
Labels
kind/health
For CI/testing/release process/refactoring/technical debt items
priority/p3
should be done in the next 6 months
triage/accepted
there is consensus amongst maintainers that this is a real bug or a reasonable feature to add
Comments
NoureldinYosri
added
the
kind/health
For CI/testing/release process/refactoring/technical debt items
label
Jun 18, 2024
cc: @pavoljuhas |
NoureldinYosri
added
the
triage/discuss
Needs decision / discussion, bring these up during Cirq Cynque
label
Jun 18, 2024
I suppose the issue is which of the support-window policies should we adopt. Let us discuss at the next cirq-cynq meeting. |
NoureldinYosri
added
triage/accepted
there is consensus amongst maintainers that this is a real bug or a reasonable feature to add
priority/p3
should be done in the next 6 months
and removed
triage/discuss
Needs decision / discussion, bring these up during Cirq Cynque
labels
Jul 3, 2024
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Labels
kind/health
For CI/testing/release process/refactoring/technical debt items
priority/p3
should be done in the next 6 months
triage/accepted
there is consensus amongst maintainers that this is a real bug or a reasonable feature to add
Description of the issue
The recommendation from scientific python is to drop python 3.10 by 2024Q4. NumPy however will drop py3.10 by April 2025. I think Cirq should drop py3.10 within the next two quarters to avoid having compatibility issues with other scientific libraries.
The text was updated successfully, but these errors were encountered: