Skip to content

Pin pyerfa to fix test failures with version 1.7.2 - #11308

Merged
pllim merged 1 commit into
astropy:masterfrom
saimn:pin-pyerfa
Feb 8, 2021
Merged

pllim merged 1 commit into
astropy:masterfrom
saimn:pin-pyerfa

Conversation

@saimn

@saimn saimn commented Feb 8, 2021

Copy link
Copy Markdown
Contributor

Ref #11305

Comment thread setup.cfg
install_requires =
numpy>=1.17
pyerfa>=1.7
pyerfa>=1.7,<1.7.2

Copy link
Copy Markdown
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Btw, we also have a requires = block above which I think is useless. But will keep that for another PR.
https://setuptools.readthedocs.io/en/latest/references/keywords.html

requires is superseded by install_requires and should not be used anymore.

Comment thread setup.cfg
install_requires =
numpy>=1.17
pyerfa>=1.7
pyerfa>=1.7,<1.7.2

Copy link
Copy Markdown
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Maybe this is safer in case we decided that the bug is really upstream and we can never use astropy with this particular bug fix version? (Not sure about the syntax itself.)

Suggested change
pyerfa>=1.7,<1.7.2
pyerfa>=1.7,!=1.7.2

Copy link
Copy Markdown
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Not sure which one is best, it could also be that tests on Astropy need to be updated. So we can update this when @mhvk can have a look.

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Yes, definitely some tests in astropy need to be updated. But I don't understand the test that you first found to fail... Anyway, good to not have to worry about breaking unrelated builds!!!!

Copy link
Copy Markdown
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I think the one in PR is better, as we can't yet guarantee that we would be compatible with any of the future versions. In the past, there was only one version bundled, so it's probably not as a big deal to stay very restrictive within astropy.
(Ideally, we should be stating upper bounds on versions, too, hopefully, the package resolvers will get better support for that soonish)

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Yes, agree that for now to just effectively pick a given version is best. I do hope to get around to fixing the astropy tests soon, and will try to make it version-dependent, as we do for numpy.

@pllim pllim left a comment

Copy link
Copy Markdown
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Okay, let's get this in to remove block... Thanks!

@pllim pllim added zzz 💤 merge-when-ci-passes Do not use: We have auto-merge option now. and removed Upstream Action Required Was: Upstream Fix Required labels Feb 8, 2021
@pllim

pllim commented Feb 8, 2021 •

Copy link
Copy Markdown
Member

Remote data job failure unrelated, though I would think the numpy nightly wheel would have been updated by now and the errors would disappear but that is another issue.

32-bit job failure also unrelated.

@pllim
pllim merged commit d80f1a1 into astropy:master Feb 8, 2021
@saimn
saimn deleted the pin-pyerfa branch February 8, 2021 15:44
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Projects

None yet

Development

Successfully merging this pull request may close these issues.

4 participants