Page MenuHome

Numpy import error on new builds for OSX
Closed, ResolvedPublic


System Information
OSX 10.12.3

Blender Version
Broken: blender-2.78.0-git20170509.717d85fb1ca-x86_64
Worked: 2.78c official

Blender cannot import the numpy module without error. Specific error is "ImportError: cannot import name 'multiarray'"

  1. Open blender
  2. Switch to python console
  3. Type "import numpy"



Event Timeline

Joel Godin (FloridaJo) triaged this task as Confirmed, Medium priority.

Same here.
OSX 10.12.4

I can't reproduce this on OSX 10.12.5.
It works for me here.

@Brecht Van Lommel (brecht), looks like you updated python to 3.5.3 but didn't rebuild numpy , mind taking a quick peek here?

I only updated the darwin 10.9 libraries for the 2.80 builds, and this bug report is about 2.78 with Python version 3.5.2 in the screenshot. So it should not have caused this issue.

However, I do get Python errors like that in the 2.80 buildbot build, a different error in the 2.78 buildbot build, and no errors in my own local builds for either version. I think there is some issue with the buildbot using old or mixed versions of Python libs, probably missing a proper CMake update when switching branches and flags somewhere.

Brecht Van Lommel (brecht) claimed this task.

Should be fixed now.

Joel Godin (FloridaJo) reopened this task as Open.Jun 7 2017, 2:49 PM

It's happening again. 06-02 build and then also today's build.

import numpy
Traceback (most recent call last):
File "<blender_console>", line 1, in <module>
ImportError: No module named 'numpy'

@ Martijn Berger (juicyfruit) Hi Martijn, how long does a fix take to propagate through the system? I ask because Jun 11 OSX build still has that problem.

Joel Godin (FloridaJo) reopened this task as Open.Jun 14 2017, 2:48 PM

Still not fixed.

And, still not fixed. Can't try out Automation nodes until it is fixed.

The directory structure was wrong, should be really fixed now with rBL61900: Fix wrong numpy directory structure in python package for macOS 10.6..

# wrong
# fixed

I verified the latest build from buildbot works now.