PlupyError#
An authoring request was rejected by the owning session.
Subclass of RuntimeError. The owning authoring session rejected a request: invalid value/type, unsupported edit, ownership/wiring constraint, stale/deleted handle, unavailable UI, Play mode, closed project, or an invocation that no longer matches the current project revision. The message identifies the cause. Do not retry an edit automatically after a host failure.
Handle type errors identify the received kind and the required kind. For example, an object datablock is different from its placement in a scene: use scene.objects for placements and the appropriate plupy.data collection for datablocks. Query the collection again when a handle has expired; a name, ID or path cannot substitute for the returned typed handle.
Errors say how to fix the call: a missing or wrong-typed argument names the method, the argument and what was received; an unknown property, input, primitive, transform channel or data.new type lists the valid ones; an unknown method lists the three closest methods. Method names are matched loosely, so sequence.track_effects, componentProps.set, use.list and scripts.attach reach sequence.trackEffects, component_props.set, uses.list and scripts.attach, and a script:Name component key means script:Name.
class PlupyError(RuntimeError)Usage and examples
Related types#
Source#
- _live.py:10