-
Notifications
You must be signed in to change notification settings - Fork 26
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
Release Candidate v1.1.0 #59
Conversation
Removed support for 3.3 and added support for 3.7.
Improved wheel logic so that no user specified environment variables are required.
Added comments containing two of the individual flags needed in comments and the general static flag as the real flag.
Improved error message
Changed static flag option since f2py doesn't use the makefile
This is giving travis coniption fits.
3.7 isn't ready for testing yet.
… is initialized properly for each test.
…g scheme of other methods.
Better error message for compilation problems.
[Feature] Ability to generate the magnetic field vector in apex coordinates.
IGRF coefficients are directly read from ASCII-file instead of using hard-coded values. This omits adding the coefficients manually in the future.
IGRF.f90 needs to be compiled first to make module available in linking.
Added some missing docstrings an simplified some tests.
Made a handful of PEP8 improvemeents and added a missing docstring.
Fixed unit tests that were failing on Travis due to a change in warning behaviour. Also added some missing docstrings and added more constraints to the unit tests under scrutiny.
Reverted style include whitespace around code pertaining to a block comment and ajusted line length.
Future-proofed the new doctrings.
Updated the changelog with a summary of updates in this pull request.
adding support for numpy.ndarray and numpy.datetime64 to helpers.subsol
modifying appveyor.yml, removing 3.4 and fix-compiler-error.py
… due to update to IGRF13
Improve robustness of unit tests for command line calls by ensuring access to apexpy on systems without the executable in the path.
Remove the extra whitespace before a comma.
Added a relative tolerance limit to `test_apxg2all` unit test.
Co-authored-by: Angeline Burrell <[email protected]>
Co-authored-by: Angeline Burrell <[email protected]>
Co-authored-by: Angeline Burrell <[email protected]>
[BUG]: Update apexshdat with IGRF13
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.
Just some polish-related comments and questions for the documentation. Otherwise it's looking good to me!
Fixed wording and spellings. Co-authored-by: Ashton Reimer <[email protected]>
Co-authored-by: Angeline Burrell <[email protected]>
Co-authored-by: Angeline Burrell <[email protected]>
Co-authored-by: Angeline Burrell <[email protected]>
Co-authored-by: Angeline Burrell <[email protected]>
The only thing left to do now might be to test this:
on macOS to see if it works without the
So it disables wheels even for the dependencies. If we want users to only rebuild the apexpy package, this seems to do that:
Changing the docs to use the above command might be the way to go so we aren't implicitly asking users to compile |
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.
After verifying the suspected issues with recommending:
pip install --global-option build_ext apexpy
to users, I updated the documentation to recommend:
pip install --no-binary :apexpy: apexpy
instead. I think this covers all the issues we had that are relevant to this release.
Release candidate for version 1.1.0.
Summary of Changes
Release Checklist