*VectorProperty types argument value COORDINATES was renamed to COORDS, breaking existing scripts #98860

New Issue

Damien Picard · 2022-06-13T21:23:59+02:00

Damien Picard commented

2022-06-13 21:23:59 +02:00

System Information
Operating system: Linux-5.15.0-37-generic-x86_64-with-glibc2.35 64 Bits
Graphics card: GeForce GTX 660M/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 418.226.00

Blender Version
Broken: version: 3.3.0 Alpha, branch: master (modified), commit date: 2022-06-13 16:29, hash: 1243c2bdae
Broken: hash: 94444aaadf
Worked: hash: fb86f3ee18

Short description of error
The Sun Position add-on is broken as of 94444aaadf.
It looks like the value COORDINATES of the subtype parameter for the *VectorProperty types was renamed to COORDS in 94444aaadf. It doesn’t look like it was intended, since the change wasn’t documented as far as I could tell.

Exact steps for others to reproduce the error

Run the following script:

import bpy
bpy.types.Scene.co = bpy.props.FloatVectorProperty(subtype='COORDINATES')

The following error is raised:

ValueError: enum identifier: 'COORDINATES' not found in ('COLOR', 'TRANSLATION', 'DIRECTION', 'VELOCITY', 'ACCELERATION', 'MATRIX', 'EULER', 'QUATERNION', 'AXISANGLE', 'XYZ', 'XYZ_LENGTH', 'COLOR_GAMMA', 'COORDS', 'LAYER', 'LAYER_MEMBER', 'NONE')
Error: Python: Traceback (most recent call last):
  File "/Text", line 2, in <module>

ValueError: bpy_struct "Scene" registration error: 'co' FloatVectorProperty could not register (see previous error)

This works fine, though:

import bpy
bpy.types.Scene.co = bpy.props.FloatVectorProperty(subtype='COORDS')

**System Information** Operating system: Linux-5.15.0-37-generic-x86_64-with-glibc2.35 64 Bits Graphics card: GeForce GTX 660M/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 418.226.00 **Blender Version** Broken: version: 3.3.0 Alpha, branch: master (modified), commit date: 2022-06-13 16:29, hash: `1243c2bdae` Broken: hash: `94444aaadf` Worked: hash: `fb86f3ee18` **Short description of error** The Sun Position add-on is broken as of 94444aaadf. It looks like the value `COORDINATES` of the subtype parameter for the *VectorProperty types was renamed to `COORDS` in 94444aaadf. It doesn’t look like it was intended, since the change wasn’t documented as far as I could tell. **Exact steps for others to reproduce the error** - Run the following script: ``` import bpy bpy.types.Scene.co = bpy.props.FloatVectorProperty(subtype='COORDINATES') ``` - The following error is raised: ``` ValueError: enum identifier: 'COORDINATES' not found in ('COLOR', 'TRANSLATION', 'DIRECTION', 'VELOCITY', 'ACCELERATION', 'MATRIX', 'EULER', 'QUATERNION', 'AXISANGLE', 'XYZ', 'XYZ_LENGTH', 'COLOR_GAMMA', 'COORDS', 'LAYER', 'LAYER_MEMBER', 'NONE') Error: Python: Traceback (most recent call last): File "/Text", line 2, in <module> ValueError: bpy_struct "Scene" registration error: 'co' FloatVectorProperty could not register (see previous error) ``` - This works fine, though: ``` import bpy bpy.types.Scene.co = bpy.props.FloatVectorProperty(subtype='COORDS') ```

Damien Picard commented

2022-06-13 21:23:59 +02:00

Added subscriber: @pioverfour

Germano Cavalcante commented

2022-06-14 20:34:33 +02:00

Added subscribers: @ideasman42, @mano-wii

Campbell Barton was assigned by Germano Cavalcante

2022-06-14 20:34:33 +02:00

Germano Cavalcante commented

2022-06-14 20:34:33 +02:00

Changed status from 'Needs Triage' to: 'Confirmed'

Germano Cavalcante commented

2022-06-14 20:34:33 +02:00

It does indeed look like it was an accident on 94444aaadf and in fact can break addons like Sun Position.

@ideasman42, can you check?

It does indeed look like it was an accident on 94444aaadf and in fact can break addons like Sun Position. @ideasman42, can you check?

blender-admin commented

2022-06-16 08:41:41 +02:00

This issue was referenced by 9bed68de13

This issue was referenced by 9bed68de134c9cc5ff5295b95cc1bf0bae97b78a

Philipp Oeser commented

2022-06-16 09:00:10 +02:00

Added subscriber: @lichtwerk

Philipp Oeser commented

2022-06-16 09:00:10 +02:00

Might not be the most critical case, will still raise priority since it would be good to get a statement on the situation (scripts either need updating - then this should be documented in the changelog - or any other solution)

Campbell Barton commented

2022-06-16 10:10:54 +02:00

Changed status from 'Confirmed' to: 'Resolved'

Campbell Barton closed this issue

2022-06-16 10:10:54 +02:00

Sign in to join this conversation.

No Label

Download

What's New

Blender Studio

Manual

Developers Blog

Documentation

Benchmark

Blender Conference

Development Fund

One-time Donations

*VectorProperty types argument value COORDINATES was renamed to COORDS, breaking existing scripts #98860