Opened 7 years ago

Closed 3 years ago

#54675 closed defect (wontfix)

py35-pandas @0.20.3_0: Missing extensions / problem importing numpy.core.multiarray

Reported by: cod3monk (Julian) Owned by: stromnov (Andrey Stromnov)
Priority: Normal Milestone:
Component: ports Version:
Keywords: Cc: chrstphrchvz (Christopher Chavez)
Port: py-pandas

Description

Panda can not be imported, due to a problem with some (missing?) extensions or unable to import from numpy:

$ python -c 'import pandas'
RuntimeError: module compiled against API version 0xb but this version of numpy is 0xa
Traceback (most recent call last):
  File "/opt/local/Library/Frameworks/Python.framework/Versions/3.5/lib/python3.5/site-packages/pandas/__init__.py", line 26, in <module>
    from pandas._libs import (hashtable as _hashtable,
  File "/opt/local/Library/Frameworks/Python.framework/Versions/3.5/lib/python3.5/site-packages/pandas/_libs/__init__.py", line 3, in <module>
    from .tslib import iNaT, NaT, Timestamp, Timedelta, OutOfBoundsDatetime
ImportError: numpy.core.multiarray failed to import

During handling of the above exception, another exception occurred:

Traceback (most recent call last):
  File "<string>", line 1, in <module>
  File "/opt/local/Library/Frameworks/Python.framework/Versions/3.5/lib/python3.5/site-packages/pandas/__init__.py", line 35, in <module>
    "the C extensions first.".format(module))
ImportError: C extension: umpy.core.multiarray failed to import not built. If you want to import pandas from the source directory, you may need to run 'python setup.py build_ext --inplace --force' to build the C extensions first.
$

non the less, I can manually import numpy.core.multiarray

$ python -c 'import numpy.core.multiarray'
$

Current versions:

$ port installed py35-pandas py35-numpy python35
The following ports are currently installed:
  py35-numpy @1.13.1_0+gfortran (active)
  py35-pandas @0.20.3_0 (active)
  python35 @3.5.4_0 (active)
$

Change History (8)

comment:1 Changed 7 years ago by cod3monk (Julian)

A build from source using pip is a workaround that solved the issue for me. Building from source using port -s did not make any difference.

comment:2 Changed 7 years ago by Schamschula (Marius Schamschula)

Priority: HighNormal

Please do not set priority. This field should only be set by MacPorts committers.

comment:3 Changed 7 years ago by mf2k (Frank Schima)

Owner: set to stromnov
Port: py-pandas added; py35-pandas removed
Status: newassigned

In the future, please Cc the port maintainers (port info --maintainers py35-pandas), if any.

comment:4 Changed 4 years ago by chrstphrchvz (Christopher Chavez)

RuntimeError: module compiled against API version 0xb but this version of numpy is 0xa

NumPy C API version was raised from 0xa to 0xb in 1.13.0 (it has since been raised again, most recently to 0xe in NumPy 1.19.0). This error would indicate that, despite py35-numpy @1.13.1_0 in the output of port installed, there was still NumPy < 1.13.0 somewhere which was taking precedence over py35-numpy from MacPorts. This ticket is likely invalid.

comment:5 Changed 4 years ago by chrstphrchvz (Christopher Chavez)

Cc: chrstphrchvz added

comment:6 Changed 3 years ago by ryandesign (Ryan Carsten Schmidt)

Do you still see this problem with up to date ports? We're now at py27-pandas @0.24.2, py35-pandas @0.25.3, py36/37/38/39-pandas @1.1.4.

comment:7 Changed 3 years ago by cod3monk (Julian)

I am not using py3.5 anymore. on py3.7 it works.

can be closed in my opinion as 3.5 is EOL.

comment:8 Changed 3 years ago by stromnov (Andrey Stromnov)

Resolution: wontfix
Status: assignedclosed
Note: See TracTickets for help on using tickets.