-
Notifications
You must be signed in to change notification settings - Fork 7
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 py38 #500
Conversation
@CasperWA I also added 3.11 to the CI tests. i guess if they pass, I can add that to the list of supported python versions as well. Then the versions match with aiida-core. |
@CasperWA regarding the readme compatilibty matrix, we still keep versions 1.0-1.2 compatible with AiiDA 2.0-3.0, right? It should be the case, as long as you use the don't use python 3.8. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Looks good to me - just need to update the AiiDA version range in the README for the new AiiDA-OPTIMADE version range.
Did you run pyupgrade --py39-plus
on all the files or where do the other changes come from (related to open()
and such)?
Hmm. I'd only keep it compatible with the versions of AiiDA that support Python 3.8, I suppose? |
thanks @CasperWA
I ran Regarding the compatilibity matrix, i updated according to the following:
Feel free to suggest alternatives. |
Codecov ReportAll modified and coverable lines are covered by tests ✅
Additional details and impacted files@@ Coverage Diff @@
## develop #500 +/- ##
===========================================
- Coverage 92.91% 92.90% -0.02%
===========================================
Files 33 33
Lines 1383 1381 -2
===========================================
- Hits 1285 1283 -2
Misses 98 98
Flags with carried forward coverage won't be shown. Click here to find out more.
☔ View full report in Codecov by Sentry. |
There was a problem hiding this 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.
After merging this, the currently failing dependabot PRs should be updated and hopefully they will succeed - then they should be merged and v1.2.0 should be released (probably after running CI workflows to check for any new dependency updates).
Note, the dependabot PRs should auto-update, if not, one should wait until the CI workflows running after merging this PR finish and then the PRs should be updated manually.
So I'll just finish up with merging the latest dependency updates, and then I'll release v1.2.0. Please then check everything you need is solved by v1.2.0 concerning the immediate issue(s) and subsequent requirement for dropping Python 3.8 support :) |
thanks @CasperWA! Everything works great! |
Thank you! 😄 |
fixes #499