bpy.data.node_groups is not accessible via the Python console #68053

New Issue

Jesse Kaukonen · 2019-08-01T10:58:35+02:00

Jesse Kaukonen commented

2019-08-01 10:58:35 +02:00

System Information
Operating system: Debian 10
Graphics card: Intel HD 4000

Blender Version
Broken: v 2.81 Alpha, Date 2019-07-30 20:50, Hash: 5359b7a03307 (latest daily linux 64-bit)

The following expression in the python console produces a key not found error:

bpy.data.node_groups["Shader NodeTree"]

In the scripting workspace, the executed python expressions window displays the same map access working if you go in the shader editor and perform some sort of action that operates on the node_groups map, such as changing the default shader specular value. The case sensitivity does not seem to matter - sometimes the printout window shows the string as "Shader Nodetree", sometimes as "Shader NodeTree".

Exact steps for others to reproduce the error

Start default 2.81 scene
Go to scripting workspace
Type bpy.data.node_groups["Shader NodeTree"] in the console
Using the mouse, go in the Shader editor and perform some action on the default Principled BSDF shader and observe the map being accessed in the Python expression printout window using the identical string

**System Information** Operating system: Debian 10 Graphics card: Intel HD 4000 **Blender Version** Broken: v 2.81 Alpha, Date 2019-07-30 20:50, Hash: 5359b7a03307 (latest daily linux 64-bit) The following expression in the python console produces a key not found error: ``` bpy.data.node_groups["Shader NodeTree"] ``` In the scripting workspace, the executed python expressions window displays the same map access working if you go in the shader editor and perform some sort of action that operates on the `node_groups` map, such as changing the default shader specular value. The case sensitivity does not seem to matter - sometimes the printout window shows the string as "Shader Nodetree", sometimes as "Shader NodeTree". **Exact steps for others to reproduce the error** * Start default 2.81 scene * Go to scripting workspace * Type `bpy.data.node_groups["Shader NodeTree"]` in the console * Using the mouse, go in the Shader editor and perform some action on the default Principled BSDF shader and observe the map being accessed in the Python expression printout window using the identical string ![blender_281_pythonscripting0001.png](https://archive.blender.org/developer/F7641254/blender_281_pythonscripting0001.png)

Jesse Kaukonen commented

2019-08-01 10:58:35 +02:00

Added subscriber: @gekko

Philipp Oeser commented

2019-08-01 11:10:40 +02:00

Added subscriber: @lichtwerk

Philipp Oeser commented

2019-08-01 11:10:40 +02:00

Confirmed, checking...

Philipp Oeser self-assigned this 2019-08-01 11:34:43 +02:00

Philipp Oeser commented

2019-08-01 11:34:43 +02:00

Will put on my desk for investigation

Bastien Montagne commented

2019-08-01 11:47:46 +02:00

Added subscriber: @mont29

Bastien Montagne commented

2019-08-01 11:47:46 +02:00

Changed status from 'Open' to: 'Archived'

Bastien Montagne closed this issue

2019-08-01 11:47:46 +02:00

Bastien Montagne commented

2019-08-01 11:47:46 +02:00

That is not technically a bug, although it is confusing (and a pain to handle in C code as well), 'root' node trees are not regular data-blocks, and are not available from bpy.data. They are closer to some private data of their owner (material, light, scene data-blocks), and should only be accessed through them. Thanks for the report anyway.

That is not technically a bug, although it is confusing (and a pain to handle in C code as well), 'root' node trees *are not* regular data-blocks, and are not available from `bpy.data`. They are closer to some private data of their owner (material, light, scene data-blocks), and should only be accessed through them. Thanks for the report anyway.

Philipp Oeser commented

2019-08-01 12:03:46 +02:00

@mont29: should we tweak the data-path-reporting to their respective owner then? (or is this this even imposiible? -- havent checked code yet...)
(inclined to repoen as TODO with low prio for my desk -- this has been bugging me as well, just feels like a bug -- same goes for #68054...)

@mont29: should we tweak the data-path-reporting to their respective owner then? (or is this this even imposiible? -- havent checked code yet...) (inclined to repoen as TODO with low prio for my desk -- this has been bugging me as well, just feels like a bug -- same goes for #68054...)

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

bpy.data.node_groups is not accessible via the Python console #68053