-
Notifications
You must be signed in to change notification settings - Fork 230
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
Python 3.7 End-of-Life and Upgrading to Python 3.11 #2445
Comments
#2429 was resolved by @JacksonBurns in the process of assisting @hwpang, who is resolving #2442 via #2446 |
Regarding chemprop. You wrote above and in the environment.yml file:
How significant are the changes needed, and who is best to work on it? I'm rather unfamiliar with chemprop and RMG's use of it. Could someone start a draft PR to continue discussion? |
#2456 may end up being related - we have a custom build of |
Should this be a "project" with multiple issues or and PRs? |
It wasn't |
It could be, I just don't love the projects interface - open to trying it though. |
Our build of symmetry should be replaced with this. |
Migrating this to GitHub Project Board. |
Python 3.7 is reaching end of life this summer and will no longer receive security updates. Ultimately because we distribute on Docker now we can continue to ship the outdated Python version for a while before things actually stop working, but it will atrophy.
We will need to increment our minor version of Python, preferably to 3.11 for the speed improvements and longest support window. I say this rather than just shooting for 3.8, since I believe the additional effort of incrementing 4 minor versions will not be much worse than 1 (see below).
I anticipate that this will be an absolute nightmare, but a (forced) opportunity for some cleanup.
pydas
andpydqed
were originally written in Python 2.7, hacked to get into Python 3.7, and will likely go kicking and screaming into Python 3.11pyjulia
anddiffeqpy
are both presumably locked to Python 3.7This might take long enough that we end up targeting 3.12, which promises some very nice parallelism improvements so maybe that isn't such a bad thing.
Some things we should get done (wrt clearing tech debt) before attempting this:
nosetest
topytest
and Overhaul Testing Layout #2380 as broken as nose is now, it will be even more broken-er in Python 3.11The text was updated successfully, but these errors were encountered: