-
Notifications
You must be signed in to change notification settings - Fork 17
numpy 1.23 breaks scenepick #34
Comments
I tried to reproduce, but couldn't do so with numpy 1.23.0 and scenepic 1.0.8 on Python 3.9.6 in a virtualenv. The following seems to complete without error (where test.py is the example above):
Maybe we need a bit more info on the configuration where the error occurs? |
Interesting, here's my pip freeze on a Windows machine with Python 3.8.13 environment managed through Miniconda3: numpy==1.23.0 |
Just tried with Python 3.9.12 on my machine and it still fails. Complete repro steps with miniconda:
Still results in above error, if I do:
The above error is fixed Pip freeze after installing numpy==1.22, seems like all the other modules are the same, the only difference in numpy numpy==1.22.0 |
unable to replicate with python 3.9 or 3.10 😒 |
Here is a minimal example that replicates the issue we are seeing - I think Tadas' above was not correct: import scenepic as sp
import numpy as np
scene = sp.Scene()
mesh = scene.create_mesh("a_mesh", shared_color=sp.Colors.Blue)
mesh.add_mesh_without_normals(np.zeros((5, 3), dtype=float), np.zeros((5, 3), dtype=int)) For me this works with numpy==1.22 and fails with numpy==1.23:
@matajoh - any ideas on this, currently breaking a lot of our CI :( |
I think this is the root issue: pybind/pybind11#4038 (and hence will be fixed by the next pybind11 release, or by pulling pybind11 from source at commit 479e9a5 or later). I verified that Charlie's repro leads to an array with zero-size dimensions in pybind11, which leads to |
I tried making the update to pybind11 in #35 , which is waiting on a review. |
Local test confirmed that @tjcashman's fix works so this issue can be closed 😄 |
Closing this issue as resolved, thanks for the help everyone! |
Update to numpy==1.23.0 breaks scenepic 1.0.8 (on Windows and Ubuntu).
Reproduced by using a reduced jelly example:
Leads to the following error:
Tried in a clean conda environment both with
numpy==1.22.0
andnumpy==1.23.0
with only the latter breaking.The text was updated successfully, but these errors were encountered: