API: bpy.props getter function returns KeyError instead of default value #98939
Labels
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
No due date set.
Dependencies
No dependencies set.
Reference: blender/blender#98939
Loading…
Reference in New Issue
No description provided.
Delete Branch "%!s(<nil>)"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
System Information
Operating system: Windows-8.1 64 Bits
Graphics card: NVIDIA GeForce GTX 1060 6GB/PCIe/SSE2 4.5.0 NVIDIA 466.47
Blender Version
Broken: 3.2.0, branch: master, hash:
e05e1e3691
Worked: Unknown
Short description of error
I'm not entirely sure whether it's a bug or an omission in the docs , but attempting to retrieve a
self[prop]
inside a getter function for a property that hasn't been manually set yet results in a KeyError rather than returning the default.Sample Code:
Result:
This is an issue because the docs lead the user to believe its provided example would work similarly to the default get function. That's not the case. The example won't work at all, it'll spit an error.
In case not returning the default is the intended behavior, it'd be good to clearly point this out in the docs, perhaps providing a code snippet that more closely mimics the default getter function behavior instead of the current sample code.
Example:
Exact steps for others to reproduce the error
Added subscriber: @crowe
Added subscriber: @PratikPB2123
Added subscriber: @OmarEmaraDev
Changed status from 'Needs Triage' to: 'Archived'
I don't think we can say there is an intended behavior, the behavior is just what the developer wrote the function to do, which in this case doesn't handle the default value.
As for writing a more comprehensive code in the documentation as you attached in your report. I think that the smaller example is intentional, as the documentation just wants to demonstrate the mechanism, not recreate the existing behavior.
So I don't think this is a bug in the documentation or the code. You can try to submit a patch to clarify the documentation a bit if you want, but not sure if the responsible developer would agree.