-
Notifications
You must be signed in to change notification settings - Fork 10
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
support for astropy 4.2? #158
Comments
Could you please submit a PR that fixes that? Are we planning to support 4.2 (which is not a long-term support release) in release 20.12? |
I have it in a branch (dirac) but I am not sure this is the best way to deal with the issue. Maybe we can test the astropy version. Can you (@weaverba137) please have a look at it and make the changes you think are necessary? I will let @sbailey answer on the long term support. |
Thanx, I'll take a look. |
20.12 will continue to use 4.0.1.post1 that is in the current NERSC desiconda installation. At the same time, for our major dependencies (numpy, scipy, astropy, fitsio) we should make an effort to support whatever the latest version is that someone would get by doing a "conda install ..." or "pip install ..." of that package. I don't think we need to put a lot of effort into making sure that our unit tests specifically check that every time, but when we come across cases like this (astropy 4.2 incompatibility) we should try to fix it when possible. |
@julienguy, do you have more work to do on the |
Please go ahead. Thanks! |
Fixed in PR #159. Closing. |
I know there is a requirement to have astropy<4.1, but I am able to run with astropy 4.2 , provided
I disable the mention to astropy._erfa.core.ErfaWarning
( in
desiutil/py/desiutil/iers.py
Line 121 in b83c2d2
The text was updated successfully, but these errors were encountered: