-
-
Notifications
You must be signed in to change notification settings - Fork 1.8k
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
Getting No module named 'astropy_iers_data'
Exception on performing import astropy.io.ascii as asciitable
#16739
Comments
Not sure who packages for "voici" but this team needs to add https://pypi.org/project/astropy-iers-data/ to their distro. Line 44 in 7f7c5ba
|
Installing I have reported this to emscripten-forge in the hope that someone can fix the WASM recipe. |
@JuanCab , is this issue considered resolved over here then? If so, please close the issue. Thanks! |
I'll do that, there's been no reaction yet on the issue. |
I'll try to contribute this upstream. astropy/astropy/tests/test_logger.py Line 9 in 04dfd24
Edit: pytest does not solve the issue |
|
Description
I am trying to update some old code I had to run with the current astropy (6.1.1) under Python 3.11 under voici (which runs it in the browser). The code is old and may not use modern best practices, I am still going to review it. That said, I am reporting it because the failure occurred when attempting an
import astropy.io.ascii as asciitable
.I am certainly aware that astropy is not responsible for compatibility with voici, but given the import command that failed, it seemed like others might run into this in similar situations. I suspect the problem may be that voici may be limited in what files it can retrieve online so that
import astropy_iers_data
might fail in this situation.Expected behavior
Code should run and read a file and display a plot.
How to Reproduce
I attempt to load my Jupyter notebook via Voici and I get the following stack trace when it attempts to
import astropy.io.ascii as asciitable
.Versions
The text was updated successfully, but these errors were encountered: