Stuck on an issue?

Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.

And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.

import _erfa fails for numpy 1.14

See original GitHub issue

On 3.2rc1 with numpy 1.14.5 installed import astropy.table fails in _erfa boiling down to this ufunc import error:

Python 3.7.3 (default, May  5 2019, 04:25:55) 
[Clang 9.0.0 (clang-900.0.39.2)] on darwin
Type "help", "copyright", "credits" or "license" for more information.
>>> import astropy.table
Traceback (most recent call last):
  File "<stdin>", line 1, in <module>
  File "/sw/lib/python3.7/site-packages/astropy/table/__init__.py", line 41, in <module>
    from .column import Column, MaskedColumn, StringTruncateWarning, ColumnInfo
  File "/sw/lib/python3.7/site-packages/astropy/table/column.py", line 26, in <module>
    from . import groups
  File "/sw/lib/python3.7/site-packages/astropy/table/groups.py", line 7, in <module>
    from .index import get_index_by_names
  File "/sw/lib/python3.7/site-packages/astropy/table/index.py", line 38, in <module>
    from astropy.time import Time
  File "/sw/lib/python3.7/site-packages/astropy/time/__init__.py", line 2, in <module>
    from .formats import *
  File "/sw/lib/python3.7/site-packages/astropy/time/formats.py", line 16, in <module>
    from astropy import _erfa as erfa
  File "/sw/lib/python3.7/site-packages/astropy/_erfa/__init__.py", line 3, in <module>
    from .core import *
  File "/sw/lib/python3.7/site-packages/astropy/_erfa/core.py", line 40, in <module>
    from . import ufunc
ValueError: expect dimension name at position 1 in "(3),(3),(),()->(3)"

With numpy 1.16.3 this succeeds, but I did not find any note that NUMPY_LT_1_16 support has already been removed.

Issue Analytics

State:
Created 4 years ago
Comments:36 (36 by maintainers)

Top GitHub Comments

2reactions

bsipoczcommented, Jun 14, 2019

To summarize the slack thread:

we see this for any downstream CI where coordinates/time/table is imported (as all use erfa).
it doesn’t matter whether conda-forge or conda default packaged packages are used, both are producing the same issue.
no issues with pip installed version combinations
@mwcraig is looking into our conda build.

2reactions

mhvkcommented, May 16, 2019

@dhomeier - thanks for all the sleuthing - at least, we understand now where the problem lies. Remains to understand how best to solve it…

Top Results From Across the Web

Numpy version issue when using astropy - Stack Overflow

I was curious so just to try, I tried import astropy and of course had the same error. Nevertheless, I do have numpy...

Troubleshooting ImportError — NumPy v1.24 Manual

The best thing to do if you see this error is to contact the maintainers of the package that is causing problem so...

NumPy 1.14.5 Release Notes

This is a bugfix release for bugs reported following the 1.14.4 release. The most significant fixes are: fixes for compilation errors on alpine...

NumPy 1.21.0 Release Notes

(This also happens for some other dtypes.) Since comparisons normally only return boolean arrays, providing any other dtype will always raise an error...

Setting up and using your development environment - NumPy

Having compiled code also means that importing NumPy from the development ... you into the Python debugger when a test fails or an...