-
Notifications
You must be signed in to change notification settings - Fork 26
Feature dtcenter/METbaseimage#30 Use Python 3.12.0 #3105
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
Conversation
… python 3.10 to 3.12.0
…json to prevent error handling float32 values
…2 calls to json.dump
…ed in fire weather use case moving to numpy 2.X
Compiling on seneca using Python 3.12 results in 2 new categories of warnings.
Some options about the first one are discussed in Stack Overflow. It will apparently be fully removed from Python 3.15. Rather than holding up this PR, I will write up a separate issue to deal in MET to deal with those deprecation warnings that apparently first appeared in Python 3.11. |
…se image 3.4 and Python 3.12
@JohnHalleyGotway, I updated the references to METbaseimage v3.3 to v.3.4 and Python 3.10 to Python 3.12 in the files you listed. In the PR text, I mentioned that I did not update the version in the documentation because we have not increased the minimum python requirement from 3.10 since we confirmed that these changes still work using Python 3.10. Thanks for creating an issue to address the deprecated Python/C++ code. |
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.
I approve of these changes.
Thanks for the updates and confirming the detail about the documentation. As we move forward with future versions, seems like we really should test with Python 3.10 at some frequency to confirm that the minimum version continues to work.
This PR will switch MET to using the v3.4 METbaseimage which contains Python 3.12.0, so MET will use Python 3.12.0 for Python Embedding.
Expected Differences
Do these changes introduce new tools, command line arguments, or configuration file options? [No]
If yes, please describe:
Do these changes modify the structure of existing or add new output data types (e.g. statistic line types or NetCDF variables)? [No]
If yes, please describe:
Pull Request Testing
Confirm all tests pass
Note: I did NOT update the python requirements in the documentation because the changes to support Python 3.12.0 were backwards compatible with Python 3.10.4. The minimum requirements didn't change.
Do these changes include sufficient testing updates? [Yes]
Will this PR result in changes to the MET test suite? [No]
If yes, describe the new output and/or changes to the existing output:
Will this PR result in changes to existing METplus Use Cases? [Yes]
If yes, create a new Update Truth METplus issue to describe them.
dtcenter/METplus#2925
Do these changes introduce new SonarQube findings? [No]
If yes, please describe:
Please complete this pull request review by 3/13/2025.
Pull Request Checklist
See the METplus Workflow for details.
Select: Reviewer(s) and Development issue
Select: Milestone as the version that will include these changes
Select: Coordinated METplus-X.Y Support project for bugfix releases or MET-X.Y.Z Development project for official releases
… python 3.10 to 3.12.0… python 3.10 to 3.12.0