-
Notifications
You must be signed in to change notification settings - Fork 1
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
RC 0.3.5 #120
Conversation
Update develop with v0.3.4
MAINT: update GA workflows
Added funding acknowledgements to the repository and documentation.
Added a summary of changes to the changelog.
Updated the main repository init header.
Updated the instrument headers with the NRL pub release.
Updated the Instrument methods headers with the NRL pub release statement.
Updated the methods headers with the NRL pub release statement and improved the docstrings.
Updated the headers for the unit test files, improved the docstrings, and updated some comments.
Updated the utils headers to include the NRL pub release.
Updated the docstrings to remove formatting characters and fixed lines that were too long for PEP8.
Remove extra lines and capitalize planet's name.
Improved spacing in the documentation, line length in the readme, and added a link to the full package documentation in the documentation section of the readme.
Removed the extra "poweredbypysat" figure from the main directory.
Removed trailing whitespace from the docstring.
Added a yaml for ReadTheDocs.
NRL pub release
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! Sorry for the delay. Saw this review request in my messages today.
One request, can my institution in the zenodo document be updated to Cosmic Studio ?
Thanks for catching that. Fixed it. |
@aburrell, I was updating the date to finish this off and found a new apexpy related bug:
|
Looks like that could be related to the release of numpy 2.0.0 😿. It'll probably (?) be fixed if you limit the numpy version to 1.X. On a more positive note, I think if you specify the compilers, you can get apexpy installed on the MacOS tests. |
Try to fix apexpy installation.
Remove tabs from yaml.
Fix errors in apexpy installation attempt.
Added an uninstall line for numpy to fix downgrade. Also fixed the gcc calls.
Replaced tab with spaces.
Added lines to find gcc and a potential fix for uninstalling numpy.
Fix the limited numpy install to use a good max version number and changed the gcc debug statements.
Remove the numpy fix attempt
Removed tab from yaml.
Only test apexpy with oldest numpy.
The 'only-if-needed' is upgrading numpy to latest.
Try changing the numpy install order.
Downgrade scipy for NEP29.
Ok, I fixed the MacOS installation, but couldn't get GA to downgrade numpy for the apexpy install. So, I toggled current testing to NEP29 only. This lead to the uncovering of a bug, where you were never testing NEP29. So I also fixed NEP29. The apexpy numpy 2.0.0 issues are documented, and it can run with numpy 2.0.0 if you install with a lower version of numpy. So we'll work on that for a new release. |
Description
RC for v0.3.5
Checklist:
CHANGELOG.md
, summarizing the changesIf this is a release PR, replace the first item of the above checklist with the
release checklist on the pysat wiki:
https://github.com/pysat/pysat/wiki/Checklist-for-Release