Work towards a 2.0 release #130
Merged
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
The developer tooling and build infrastructure is completely revised, bringing the following benefits: * Automated testing is back via Github Actions * Build using pyproject.toml and the setuptools backend for compatibility with modern packaging tooling. This will allow the package to be built and distributed more easily.
I've removed any mention of the cdms interface from the documentation since cdms itself is no longer maintained. This allows the docs to build and I'll be removing the cdms interface shortly anyway.
|
well，the old one documentation page has gone ? |
|
Yes, it was replaced with the new one. Not a lot changed though so hopefully not important. |
|
yea, I've updated to 2.0，usage is the same. en，There is a question puzzling me now， I found the divergence caculated by Metpy and Windspharm are quite a different from each other, I wish I have done the right way. So, is that true? If it is，would you mind to tell me why for this? or how can I find the answer to take metpy or the windspharm in my situation。 Longing for your reply，Thanks a lot !
…---- Replied Message ----
| From | Andrew ***@***.***> |
| Date | 11/21/2024 17:56 |
| To | ajdawson/windspharm ***@***.***> |
| Cc | DoneX ***@***.***>,
Comment ***@***.***> |
| Subject | Re: [ajdawson/windspharm] Work towards a 2.0 release (PR #130) |
Yes, it was replaced with the new one. Not a lot changed though so hopefully not important.
—
Reply to this email directly, view it on GitHub, or unsubscribe.
You are receiving this because you commented.Message ID: ***@***.***>
|
|
Please open a new issue with more details if you wish to discuss the divergence calculation in more detail. You will need to provide an example of what you did, and how the results differ. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
This is most of the things I can think of that need doing. Replacing the build system is essential for continued distribution of the package. The new CI workflows are intended to replace the previously inactive ones, so testing of pull requests etc. works again. Documentation is revised so it builds with latest sphinx. Perhaps most significant is removal of cdms interface due to lack of support for the backend cdms2 package.