Page MenuHome

archipack bug
Closed, ResolvedPublic


Traceback (most recent call last):

File "/Volumes/Blender/", line 351, in enable
  mod = __import__(module_name)
File "/Volumes/Blender/", line 69, in <module>
  from . import archipack_manipulator
File "/Volumes/Blender/", line 43, in <module>
  from .archipack_gl import (
File "/Volumes/Blender/", line 32, in <module>
  import numpy as np
File "/Volumes/Blender/", line 142, in <module>
  from . import add_newdocs
File "/Volumes/Blender/", line 13, in <module>
  from numpy.lib import add_newdoc
File "/Volumes/Blender/", line 8, in <module>
  from .type_check import *
File "/Volumes/Blender/", line 11, in <module>
  import numpy.core.numeric as _nx
File "/Volumes/Blender/", line 35, in <module>
  from . import _internal  # for freeze programs
File "/Volumes/Blender/", line 15, in <module>
  import ctypes
File "/Volumes/Blender/", line 543, in <module>
File "/Volumes/Blender/", line 273, in _reset_cache
  CFUNCTYPE(c_int)(lambda: None)


bpy.context.area.ui_type = 'INFO'

//I installed the new blender and that's what happens when I try to enter the archipack//

System Information
Operating system: Darwin-18.6.0-x86_64-i386-64bit 64 Bits
Graphics card: AMD Radeon Pro 570 OpenGL Engine ATI Technologies Inc. 4.1 ATI-2.9.26

Blender Version
Broken: version: 2.80 (sub 74), branch: master, commit date: 2019-07-11 13:50, hash: rB06312c6d2db8
Worked: (optional)

Short description of error
[Please fill out a short description of the error here]

Exact steps for others to reproduce the error
[Please describe the exact steps needed to reproduce the issue]
[Based on the default startup or an attached .blend file (as simple as possible)]



Event Timeline

Philipp Oeser (lichtwerk) triaged this task as Waiting for Developer to Reproduce priority.

@Brecht Van Lommel (brecht): I think this is solved with your commits, right?

I assume the current buildbot build from is fine anyways, but for the next RC, we should also be good?

Brecht Van Lommel (brecht) claimed this task.

Re-downloading the current RC should also solve this problem.