Traceback (most recent call last):
File "<input>", line 1, in <module>
File ".../.venv/lib/python3.10/site-packages/pyrender/viewer.py", line 300, in __init__
zfar = max(scene.scale * 10.0, DEFAULT_Z_FAR)
File ".../.venv/lib/python3.10/site-packages/pyrender/scene.py", line 254, in scale
return np.linalg.norm(self.extents)
File ".../.venv/lib/python3.10/site-packages/pyrender/scene.py", line 248, in extents
return np.diff(self.bounds, axis=0).reshape(-1)
File ".../.venv/lib/python3.10/site-packages/pyrender/scene.py", line 226, in bounds
corners_local = trimesh.bounds.corners(mesh.bounds)
File ".../.venv/lib/python3.10/site-packages/pyrender/mesh.py", line 87, in bounds
bounds = np.array([[np.infty, np.infty, np.infty],
File ".../.venv/lib/python3.10/site-packages/numpy/__init__.py", line 397, in __getattr__
raise AttributeError(
AttributeError: `np.infty` was removed in the NumPy 2.0 release. Use `np.inf` instead.. Did you mean: 'info'?
For full documentation here the contents of my venv:
I think this is quite a urgent issue since new installations of pyrender break.
The new major release of numpy brings braking changes in the api making pyrender not compatible with it.
A quick fix could be giving an upper bound to the numpy dependency in
setup.py
For example this code raise an
AttributeError
when pyrender try to usenp.infty
:Traceback:
For full documentation here the contents of my venv: