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

Astropy cache warnings #20

Open
sfair opened this issue May 25, 2020 · 2 comments
Open

Astropy cache warnings #20

sfair opened this issue May 25, 2020 · 2 comments
Labels
question Further information is requested

Comments

@sfair
Copy link
Collaborator

sfair commented May 25, 2020

After a clean install of SORA (v0.1) and Anaconda (v2020.02) on OSX Catalina, I got these two warnings:

WARNING: WrongDBMModuleWarning: Existing astropy cache is in an unsupported format, either install the appropriate package or use astropy.utils.data.clear_download_cache() to delete the whole cache; db type is dbm.gnu, but the module is not available [astropy.utils.data]

WARNING: leap-second auto-update failed due to the following exception: WrongDBMModule('Existing astropy cache is in an unsupported format, either install the appropriate package or use astropy.utils.data.clear_download_cache() to delete the whole cache; db type is dbm.gnu, but the module is not available') [astropy.time.core]

This happens to all provided exemples. The notebooks seem to run properly, though.

I'm unsure wether the code should address this issue or not.

@altairgomes
Copy link
Collaborator

It seems this happens when you changes the environment of the use of astropy, for instance, from pip-based to conda-based. And it tries to read the cache whish is in another format.

Which version of Astropy are you using? They seem to already have made some modification concerning this warning: astropy/astropy#9656.

Anyway. I think this should happen only once. Have you tried again to see if the warning reappears? Also, maybe try to clean the cache using astropy.utils.data.clear_download_cache() as it is suggested.

@altairgomes altairgomes added the question Further information is requested label May 26, 2020
@sfair
Copy link
Collaborator Author

sfair commented May 27, 2020

It's astropy v4.0.

It happens only once each time a notebook is run, and it's harmless.
clear_download_cache() solves the problem.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
question Further information is requested
Projects
None yet
Development

No branches or pull requests

2 participants