Skip to content
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.

Sign up for GitHub

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

Jump to bottom

Drop python 3.10 #6648

Open
NoureldinYosri opened this issue Jun 18, 2024 · 2 comments
Open

Drop python 3.10 #6648

NoureldinYosri opened this issue Jun 18, 2024 · 2 comments
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
Milestone
2025-T6: Code hea...

Comments

@NoureldinYosri
Copy link
Collaborator

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.
@NoureldinYosri NoureldinYosri added the kind/health For CI/testing/release process/refactoring/technical debt items label Jun 18, 2024
@NoureldinYosri
Copy link
Collaborator Author

cc: @pavoljuhas

@NoureldinYosri NoureldinYosri added the triage/discuss Needs decision / discussion, bring these up during Cirq Cynque label Jun 18, 2024
@pavoljuhas
Copy link
Collaborator

I suppose the issue is which of the support-window policies should we adopt.
The difference between scientific python and NEP-29 is that NEP-29 only covers Python and NumPy and suggests 3.5 year window for Python and 2 year window for NumPy.
Scientific Python covers more science packages and advises 3 year support for Python and 2 years for everything else.

Let us discuss at the next cirq-cynq meeting.

@NoureldinYosri 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
Assignees
No one assigned
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
Projects
Cirq 2025 roadmap
Status: No status
Milestone
2025-T6: Code health and project main...
Development

No branches or pull requests
3 participants
@mhucka @pavoljuhas @NoureldinYosri