Skip to content

Drop python 3.10 support#434

Open
astafan8 wants to merge 5 commits intomasterfrom
astafan8/drop310
Open

Drop python 3.10 support#434
astafan8 wants to merge 5 commits intomasterfrom
astafan8/drop310

Conversation

@astafan8
Copy link
Collaborator

as python 3.10 is end-of-life.

@astafan8 astafan8 requested a review from jenshnielsen March 13, 2025 15:15
@astafan8 astafan8 self-assigned this Mar 13, 2025
@astafan8 astafan8 enabled auto-merge March 13, 2025 15:16
@marcosfrenkel
Copy link
Collaborator

I don't know if its time to end support for 3.10 just yet. It still has more than a year left and we use it in the lab currently

@astafan8
Copy link
Collaborator Author

astafan8 commented Apr 9, 2025

@marcosfrenkel you're right, i shoudlv'e been more clear, it's not end of life but it won't be receiving updates and fixes anymore.

we use it in the lab currently

ok, that's fair. I do encourage you to move to python 3.12 and use the latest features including performance improvements. Note that most of scientific stack follows this version support approach https://scientific-python.org/specs/spec-0000/#support-window , so most packages will stop or have already stopped publishing imporvements and features for python 3.10.

Let me know when you move to later python versions, I can then proceed with this PR.

@astafan8
Copy link
Collaborator Author

astafan8 commented Oct 6, 2025

dear @marcosfrenkel , is python 3.10 still used in your lab? qcodes dropped it already, so likely you don't get the latest qcodes versions with improvements and such. Moreover, we'd like to update plottr to use a new feature of explicitly opening the qcodes database file in read-only or read-and-also-write modes (which improves things on data reading/writing side), and if python 3.10 is to still be supported by plottr, then the update would have additional if/else statements. So let me know if python 3.10 compatibility should be retained or not anymore?

Copy link
Contributor

@wpfff wpfff left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

This looks good to me, i personally think we should go ahead and drop outdated dependencies strictly unless it clearly breaks anything.

@marcosfrenkel -- i think people in the lab should update relatively frequently.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants