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

import astropy.io.fits fails in astropy==2.0.11 #176

Closed
o-smirnov opened this issue Jan 4, 2019 · 7 comments
Closed

import astropy.io.fits fails in astropy==2.0.11 #176

o-smirnov opened this issue Jan 4, 2019 · 7 comments
Assignees
Milestone

Comments

@o-smirnov
Copy link

In [1]: import astropy.io.fits as pyfits
   ...: 
---------------------------------------------------------------------------
ImportError                               Traceback (most recent call last)
ImportError: No module named _multiarray_umath

In [2]:                                                                                                                                                                                   

Works fine in 2.0.10.

@o-smirnov
Copy link
Author

Hmmm, the plot thickens. It depends on which Ubuntu.

On Ubuntu 16.04, both 2.0.10 and 2.0.11 print the error above.

On Ubuntu 18.04, 2.0.10 is OK but 2.0.11 prints the error.

(I'm trying to import it in two otherwise identical virtual environments...)

I should rather say warning, as it proceeds to run afterwards anyway.

@gijzelaerr gijzelaerr added this to the KERN-5 milestone Jan 8, 2019
@gijzelaerr
Copy link
Member

I can't replicate the issue on Ubuntu 18.04, python2 and 2.0.11 (virtualenv, tshikovski)

@gijzelaerr gijzelaerr self-assigned this Jan 9, 2019
@gijzelaerr
Copy link
Member

this is just not a KERN issue, closing this.

@o-smirnov
Copy link
Author

@bennahugo, I first saw this here...

@gijzelaerr
Copy link
Member

hm?

@o-smirnov
Copy link
Author

Seeing the same error in a different context. Still haven't figured it out.

@gijzelaerr
Copy link
Member

did you experiment with the numpy version? Some googlin hints that this might be a numpy 1.15 issue and running 1.16 solved it.

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

No branches or pull requests

2 participants