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.

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

Merged
merged 9 commits into from
Nov 6, 2023
Merged

Drop py38 #500

merged 9 commits into from
Nov 6, 2023

Conversation

eimrek
Copy link
Member

@eimrek eimrek commented Nov 2, 2023

fixes #499

@eimrek
Copy link
Member Author

eimrek commented Nov 2, 2023

@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.

@eimrek
Copy link
Member Author

eimrek commented Nov 2, 2023

@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.

@eimrek eimrek requested a review from CasperWA November 2, 2023 13:51
Copy link
Collaborator

@CasperWA CasperWA left a 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)?

README.md Outdated Show resolved Hide resolved
@CasperWA
Copy link
Collaborator

CasperWA commented Nov 6, 2023

@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.

Hmm. I'd only keep it compatible with the versions of AiiDA that support Python 3.8, I suppose?

@eimrek
Copy link
Member Author

eimrek commented Nov 6, 2023

thanks @CasperWA

Did you run pyupgrade --py39-plus on all the files or where do the other changes come from (related to open() and such)?

I ran pyupgrade --py37-plus before (that changed open()) but now also pyupgrade --py39-plus, which introduced many changes to the typing library imports.

Regarding the compatilibity matrix, i updated according to the following:

  • aiida >=2.0.0, <2.4.0 is compatible with py3.8, so i used that range for 1.0-1.2
  • aiida >=2.2.0 is compatible with py 3.11, so i used that for the new version that will also be compatible with py3.11.

Feel free to suggest alternatives.

@eimrek eimrek requested a review from CasperWA November 6, 2023 12:05
Copy link

codecov bot commented Nov 6, 2023

Codecov Report

All modified and coverable lines are covered by tests ✅

Comparison is base (04c7d2d) 92.91% compared to head (6fba496) 92.90%.
Report is 1 commits behind head on develop.

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              
Flag Coverage Δ
aiida 89.21% <96.66%> (-0.02%) ⬇️
mongo 79.72% <100.00%> (-0.03%) ⬇️

Flags with carried forward coverage won't be shown. Click here to find out more.

Files Coverage Δ
aiida_optimade/cli/cmd_init.py 99.20% <100.00%> (ø)
aiida_optimade/entry_collections.py 98.72% <100.00%> (ø)
aiida_optimade/mappers/entries.py 95.83% <100.00%> (ø)
aiida_optimade/mappers/structures.py 89.18% <100.00%> (-0.29%) ⬇️
aiida_optimade/translators/entities.py 86.30% <100.00%> (ø)
aiida_optimade/translators/structures.py 91.17% <100.00%> (ø)
aiida_optimade/translators/utils.py 89.18% <100.00%> (ø)
aiida_optimade/utils.py 100.00% <ø> (ø)

☔ View full report in Codecov by Sentry.
📢 Have feedback on the report? Share it here.

Copy link
Collaborator

@CasperWA CasperWA 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.

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.

@CasperWA CasperWA enabled auto-merge (squash) November 6, 2023 12:25
@CasperWA CasperWA merged commit 1d3a7eb into develop Nov 6, 2023
9 checks passed
@CasperWA CasperWA deleted the drop-py38 branch November 6, 2023 12:32
@eimrek
Copy link
Member Author

eimrek commented Nov 6, 2023

thanks @CasperWA the PRs didnt seem to get updated automatically. I merged develop into the aiida update PR #484. Is this what you meant? If that's fine i'll do the same for #482 as well.

@CasperWA
Copy link
Collaborator

CasperWA commented Nov 6, 2023

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 :)

@eimrek
Copy link
Member Author

eimrek commented Nov 7, 2023

thanks @CasperWA! Everything works great!

@CasperWA
Copy link
Collaborator

CasperWA commented Nov 7, 2023

thanks @CasperWA! Everything works great!

Thank you! 😄

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.

Drop python 3.8 support
2 participants