SystemError setting ID custom property to a list containing NumPy scalars #117656

Open
opened 2024-01-30 03:23:25 +01:00 by Thomas Barlow · 3 comments
Member

System Information
Operating system: Windows-10-10.0.19045-SP0 64 Bits
Graphics card: NVIDIA GeForce GTX 1070 Ti/PCIe/SSE2 NVIDIA Corporation 4.6.0 NVIDIA 546.33

Blender Version
Broken: version: 4.1.0 Alpha, branch: main, commit date: 2024-01-29 00:53, hash: dab651537471
Worked: (newest version of Blender that worked as expected)

Short description of error
Trying to set an id prop array to a list containing numpy scalars (or another sequence that is not considered a compatible buffer) raises a SystemError when run from the Python Console (or a delayed TypeError when run from the Text Editor and another line checks for an exception being set afterward):

Error: Python: TypeError: object of type 'numpy.int32' has no len()

The above exception was the direct cause of the following exception:

Traceback (most recent call last):
  File "D:\Downloads\blender-4.1.0-alpha+main.dab651537471-windows.amd64-release\4.1\scripts\modules\console_python.py", line 149, in execute
    with (
SystemError: <function _TempModuleOverride.__exit__ at 0x000001DC9D302D40> returned a result with an exception set

On a debug build, an assertion instead fails in Python itself:

Assertion failed: !PyErr_Occurred(), file C:\db\build\S\VS1564D\build\python\src\external_python\Objects\typeobject.c, line 3823

Exact steps for others to reproduce the error
Run in the Python Console:

import numpy as np
bpy.context.scene['test_id_prop'] = list(np.array([0]))

or (because id prop arrays do not support 64-bit int and the array will not be considered a compatible buffer)

import numpy as np
bpy.context.scene['test_id_prop'] = np.array([0], dtype=np.int64)
**System Information** Operating system: Windows-10-10.0.19045-SP0 64 Bits Graphics card: NVIDIA GeForce GTX 1070 Ti/PCIe/SSE2 NVIDIA Corporation 4.6.0 NVIDIA 546.33 **Blender Version** Broken: version: 4.1.0 Alpha, branch: main, commit date: 2024-01-29 00:53, hash: `dab651537471` Worked: (newest version of Blender that worked as expected) **Short description of error** Trying to set an id prop array to a list containing numpy scalars (or another sequence that is not considered a compatible buffer) raises a `SystemError` when run from the Python Console (or a delayed TypeError when run from the Text Editor and another line checks for an exception being set afterward): ``` Error: Python: TypeError: object of type 'numpy.int32' has no len() The above exception was the direct cause of the following exception: Traceback (most recent call last): File "D:\Downloads\blender-4.1.0-alpha+main.dab651537471-windows.amd64-release\4.1\scripts\modules\console_python.py", line 149, in execute with ( SystemError: <function _TempModuleOverride.__exit__ at 0x000001DC9D302D40> returned a result with an exception set ``` On a debug build, an assertion instead fails in Python itself: ``` Assertion failed: !PyErr_Occurred(), file C:\db\build\S\VS1564D\build\python\src\external_python\Objects\typeobject.c, line 3823 ``` **Exact steps for others to reproduce the error** Run in the Python Console: ``` import numpy as np bpy.context.scene['test_id_prop'] = list(np.array([0])) ``` or (because id prop arrays do not support 64-bit int and the array will not be considered a compatible buffer) ``` import numpy as np bpy.context.scene['test_id_prop'] = np.array([0], dtype=np.int64) ```
Thomas Barlow added the
Type
Report
Priority
Normal
Status
Needs Triage
labels 2024-01-30 03:23:26 +01:00
Member

Thanks for the report. Can confirm. Seems to work with other dtypes (int_, float_, int32)

Thanks for the report. Can confirm. Seems to work with other dtypes (int_, float_, int32)
Pratik Borhade added
Module
Python API
Status
Confirmed
and removed
Status
Needs Triage
labels 2024-01-30 07:56:15 +01:00
Contributor

A note that setting numpy array of numpy np.int32 does work without errors though (C.object['np_data'] = np.array([3,4,5])), error occurs only when np.int32 are in default python list.

A note that setting numpy array of numpy np.int32 does work without errors though (`C.object['np_data'] = np.array([3,4,5])`), error occurs only when np.int32 are in default python list.
Author
Member

A note that setting numpy array of numpy np.int32 does work without errors though (C.object['np_data'] = np.array([3,4,5])), error occurs only when np.int32 are in default python list.

The np.int32 array works because it runs a different code path. Numpy arrays implement the Buffer Protocol and the code responsible for reading the elements in the array sees this and that the format (element type) of the buffer is compatible and then reads the elements of the array directly from the array's memory.

Python lists don't implement the Buffer Protocol, so the code has to iterate the list similar to a for loop written in Python and somewhere in that iteration the error occurs.

I think it may relate to either how numpy scalars can be accessed like read-only zero-dimensional arrays:

zero_dim_array = np.array(6, dtype=np.int32)
# 6
print(zero_dim_array[()])

scalar = np.int32(12)
# 12
print(scalar[()])

or how numpy scalars also implement the buffer protocol:

x = np.int32(12)
# Would error if `x` was not a buffer
mv = memoryview(x)

with the code then incorrectly assuming that having one of these properties means that __len__() should be implemented.

I'm guessing it maybe tries to read each numpy scalar as a sequence rather than as a long in e3894f0a07/source/blender/python/generic/idprop_py_api.cc (L678) since np.int32 is not a subclass of Python int so I think will fail PyLong_Check()

> A note that setting numpy array of numpy np.int32 does work without errors though (`C.object['np_data'] = np.array([3,4,5])`), error occurs only when np.int32 are in default python list. The np.int32 array works because it runs a different code path. Numpy arrays implement the Buffer Protocol and the code responsible for reading the elements in the array sees this and that the format (element type) of the buffer is compatible and then reads the elements of the array directly from the array's memory. Python lists don't implement the Buffer Protocol, so the code has to iterate the list similar to a for loop written in Python and somewhere in that iteration the error occurs. I think it may relate to either how numpy scalars can be accessed like read-only zero-dimensional arrays: ```py zero_dim_array = np.array(6, dtype=np.int32) # 6 print(zero_dim_array[()]) scalar = np.int32(12) # 12 print(scalar[()]) ``` or how numpy scalars also implement the buffer protocol: ```py x = np.int32(12) # Would error if `x` was not a buffer mv = memoryview(x) ``` with the code then incorrectly assuming that having one of these properties means that `__len__()` should be implemented. I'm guessing it maybe tries to read each numpy scalar as a sequence rather than as a long in https://projects.blender.org/blender/blender/src/commit/e3894f0a0708d1619dbfce3fb081f12bcee3f0c3/source/blender/python/generic/idprop_py_api.cc#L678 since `np.int32` is not a subclass of Python `int` so I think will fail `PyLong_Check()`
Sign in to join this conversation.
No Label
Interest
Alembic
Interest
Animation & Rigging
Interest
Asset Browser
Interest
Asset Browser Project Overview
Interest
Audio
Interest
Automated Testing
Interest
Blender Asset Bundle
Interest
BlendFile
Interest
Collada
Interest
Compatibility
Interest
Compositing
Interest
Core
Interest
Cycles
Interest
Dependency Graph
Interest
Development Management
Interest
EEVEE
Interest
EEVEE & Viewport
Interest
Freestyle
Interest
Geometry Nodes
Interest
Grease Pencil
Interest
ID Management
Interest
Images & Movies
Interest
Import Export
Interest
Line Art
Interest
Masking
Interest
Metal
Interest
Modeling
Interest
Modifiers
Interest
Motion Tracking
Interest
Nodes & Physics
Interest
OpenGL
Interest
Overlay
Interest
Overrides
Interest
Performance
Interest
Physics
Interest
Pipeline, Assets & IO
Interest
Platforms, Builds & Tests
Interest
Python API
Interest
Render & Cycles
Interest
Render Pipeline
Interest
Sculpt, Paint & Texture
Interest
Text Editor
Interest
Translations
Interest
Triaging
Interest
Undo
Interest
USD
Interest
User Interface
Interest
UV Editing
Interest
VFX & Video
Interest
Video Sequencer
Interest
Virtual Reality
Interest
Vulkan
Interest
Wayland
Interest
Workbench
Interest: X11
Legacy
Blender 2.8 Project
Legacy
Milestone 1: Basic, Local Asset Browser
Legacy
OpenGL Error
Meta
Good First Issue
Meta
Papercut
Meta
Retrospective
Meta
Security
Module
Animation & Rigging
Module
Core
Module
Development Management
Module
EEVEE & Viewport
Module
Grease Pencil
Module
Modeling
Module
Nodes & Physics
Module
Pipeline, Assets & IO
Module
Platforms, Builds & Tests
Module
Python API
Module
Render & Cycles
Module
Sculpt, Paint & Texture
Module
Triaging
Module
User Interface
Module
VFX & Video
Platform
FreeBSD
Platform
Linux
Platform
macOS
Platform
Windows
Priority
High
Priority
Low
Priority
Normal
Priority
Unbreak Now!
Status
Archived
Status
Confirmed
Status
Duplicate
Status
Needs Info from Developers
Status
Needs Information from User
Status
Needs Triage
Status
Resolved
Type
Bug
Type
Design
Type
Known Issue
Type
Patch
Type
Report
Type
To Do
No Milestone
No project
No Assignees
3 Participants
Notifications
Due Date
The due date is invalid or out of range. Please use the format 'yyyy-mm-dd'.

No due date set.

Dependencies

No dependencies set.

Reference: blender/blender#117656
No description provided.