-
Notifications
You must be signed in to change notification settings - Fork 28
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
devdeps failing with "ModuleNotFoundError: No module named 'pyarrow'" #1481
Comments
@mairanteodoro is there a requirement to test all these formats? If so we may need to add some more test dependencies. |
Not that I know of, @braingram. |
Confirming, yes, we need only support a small number of formats, maybe fits and ecsv. asdf is also good though I actually don't know what schema would be being used for that catalog. @mairanteodoro , if you have time, cleaning this up to be more minimal so it doesn't affect devdeps testing would be great, thanks. |
Work done in PR#1496. |
https://github.com/spacetelescope/romancal/actions/runs/11598260944/job/32293762396#step:10:922
I believe this may be due to the use of a development version of astropy.
This also appears in the downstream/devdeps testing in stcal:
https://github.com/spacetelescope/stcal/actions/runs/11597106821/job/32289791188#step:10:745
Is it necessary/useful to test all of these formats?
romancal/romancal/tweakreg/tests/test_astrometric_utils.py
Lines 484 to 493 in 2f7d065
It seems like more a test of astropy than anything romancal related.
The text was updated successfully, but these errors were encountered: