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

Astroquery v0.4.7 #872

Closed
rachel3834 opened this issue Mar 13, 2024 · 2 comments
Closed

Astroquery v0.4.7 #872

rachel3834 opened this issue Mar 13, 2024 · 2 comments
Labels
bug Something isn't working

Comments

@rachel3834
Copy link
Contributor

Describe the bug
The most recent version of astroquery appears to have changed the caching behaviour of Vizier queries. In v0.4.6 Vizier query objects have a cache_location parameter which can be set to None to switch off caching. This is desirable when a TOM is deployed to a Cloud-based server for example, since setting a cache location is a little more complicated and can incur additional charges.

Reviewing the current astropy documentation, it was not immediately obvious how this behavior can be configured in the newer version.

@rachel3834 rachel3834 added the bug Something isn't working label Mar 13, 2024
@jchate6
Copy link
Contributor

jchate6 commented Mar 15, 2024

See #871

@jchate6
Copy link
Contributor

jchate6 commented Mar 26, 2024

We have bumped the poetry.lock version of Astroquery to 0.4.7
We still support earlier versions of astroquery, but vizier is not used in TomBase.
If you run into the above issue, you may need to restrict the astroquery version to astroquery = "<0.4.7" in your TOM.

@jchate6 jchate6 closed this as completed Mar 26, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working
Projects
Archived in project
Development

No branches or pull requests

2 participants