Astroquery should be strictly pinned #237
Merged
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Contributor
|
Thanks! |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
We started to see old issues (https://travis-ci.org/astropy/astropy-tutorials/builds/390649359#L871) that has been solved for a while upstream in astroquery (astropy/astroquery#1021).
It's not perfectly clear why the notebook started to run into it again, I suspect there may be some issues with the versions installed (#234), but as the first measure we should let the installer to pick up more recent astroqueries (given it's not like other packages, if an old version used to work, it's not guaranteed at all it still works due to its dependency on upstream services that can change beyond our control).