Conversation
|
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 |
|
@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.
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. |
|
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? |
wpfff
left a comment
There was a problem hiding this comment.
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.
as python 3.10 is end-of-life.