Skip to content
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

Closed
julienguy opened this issue Dec 17, 2020 · 7 comments
Closed

support for astropy 4.2? #158

julienguy opened this issue Dec 17, 2020 · 7 comments
Assignees

Comments

@julienguy
Copy link
Contributor

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

warnings.filterwarnings('ignore',
)

@weaverba137
Copy link
Member

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?

@julienguy
Copy link
Contributor Author

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.

@weaverba137
Copy link
Member

Thanx, I'll take a look.

@sbailey
Copy link
Contributor

sbailey commented Dec 17, 2020

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.

@weaverba137
Copy link
Member

@julienguy, do you have more work to do on the dirac branch? If not, I'll update the unit tests and convert that to a PR.

@julienguy
Copy link
Contributor Author

Please go ahead. Thanks!

@sbailey
Copy link
Contributor

sbailey commented Dec 22, 2020

Fixed in PR #159. Closing.

@sbailey sbailey closed this as completed Dec 22, 2020
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants