Skip to main content

nodebpy

Run Tests

Build node trees in Blender more elegantly with Python code. Geometry Nodes, Shader Nodes and Compositor nodes are all fully supported, with type hints and IDE auto-completion throughout.

pip install nodebpy

A text-based version of nodes should bring the convenience of writing code with IDE auto-completion, type hinting, with overall compactness and readability, while staying as close as possible to what building a node tree via the GUI feels like.

from nodebpy import geometry as g

with g.tree("AnotherTree", collapse=True, is_modifier=True) as tree:
    rot = (
        g.RandomValue.vector(min=-1, seed=2)
        >> g.AlignRotationToVector()
        >> g.RotateRotation(rotate_by=g.AxisAngleToRotation(angle=0.3))
    )
    pos = g.Position() * 2.0 + (0, 0.2, 0.3)

    (
        tree.inputs.integer("Count", 10)
        >> g.Points(position=g.RandomValue.vector(min=-1))
        >> g.InstanceOnPoints(instance=g.Cube(), rotation=rot)
        >> g.SetPosition(position=pos, offset=(0, 0, 0.1))
        >> g.RealizeInstances()
        >> g.InstanceOnPoints(g.Cube(), instance=...)
        >> tree.outputs.geometry("Instances")
    )

  • Every node is a typed class named after the node it creates — 'Random Value' becomes g.RandomValue() — and node subtypes are class methods: g.RandomValue.vector().
  • Trees are built inside a with g.tree(...): context; instantiating a node class adds it to the current tree, and the tree's interface is declared with tree.inputs.* / tree.outputs.*.
  • Nodes are linked with the >> operator, which picks the most compatible socket pair automatically (much like Node Wrangler's Alt + Right Click drag) — or address sockets explicitly through the .i.* / .o.* accessors.
  • Python's arithmetic, comparison and boolean operators create the matching Math / VectorMath / Compare / BooleanMath nodes: g.Value(1.0) * 2 + (0, 0, 1).
  • Existing node trees — including ones wired up by hand in the GUI — can be exported back to nodebpy source with to_python().

Documentation

Guides and the full node reference live at bradyajohnston.github.io/nodebpy:

Like databpy, this project started as an internal tool inside molecularnodes before being broken out into its own robustly typed and tested package.

Contributing

Development setup, running the tests and regenerating the node classes (most of src/nodebpy/nodes/ is auto-generated by the gen/ package) are covered in CONTRIBUTING.md.

Metadata

Release files for nodebpy 520.33.0

For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.

Source distribution (sdist)

Source distribution for nodebpy 520.33.0
File Size Uploaded
nodebpy-520.33.0.tar.gz 492.7 kB Details

Built distribution (wheel)

Table of built distributions (wheels) for nodebpy 520.33.0
File Interpreter ABI Platform
nodebpy-520.33.0-py3-none-any.whl Python 3 none any Details

Total release size: 1.0 MB

Release files / nodebpy-520.33.0.tar.gz

Download URL nodebpy-520.33.0.tar.gz
Size 492.7 kB
Tags Source
SHA-256 checksum
How to use checksums
0ad931e16a0a87779c9e947bf312b4d9e67bea71dd6ec79216c05f0b163afaaf
BLAKE2b-256 checksum
How to use checksums
32024e36c8e5c919d2b524c5db84865062bee83834234d472223c2ffe5f49fc7
Upload date
Uploaded using Trusted Publishing?
What is trusted publishing?
Yes
Uploaded via twine/7.0.0 CPython/3.13.14

Provenance

Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.

PyPI Publish Attestation

PyPI verified that this artifact, at this checksum, originated from the publisher listed below.

Signed by GitHub Actions, verified by PyPI on Oct 7, 2026.

Transparency log

Release files / nodebpy-520.33.0-py3-none-any.whl

Download URL nodebpy-520.33.0-py3-none-any.whl
Size 546.8 kB
Tags Python 3
SHA-256 checksum
How to use checksums
202f81cc8c054d515a99f49e0d00f91effb362ea6dd3b0a32a5e69409894f00d
BLAKE2b-256 checksum
How to use checksums
3798995be0925e5e8e6de08b1cf2aa4102640c7b8885626d7d152045eca18e8c
Upload date
Uploaded using Trusted Publishing?
What is trusted publishing?
Yes
Uploaded via twine/7.0.0 CPython/3.13.14

Provenance

Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.

PyPI Publish Attestation

PyPI verified that this artifact, at this checksum, originated from the publisher listed below.

Signed by GitHub Actions, verified by PyPI on Oct 7, 2026.

Transparency log

Release history Release notifications | RSS feed

This release

520.33.0 This release

2 release files

0.18.0

2 release files

0.17.0

2 release files

0.15.1

2 release files

0.15.0

2 release files

0.14.0

2 release files

0.13.0

2 release files

0.12.0

2 release files

0.11.1

2 release files

0.11.0

2 release files

0.10.2

2 release files

0.10.1

2 release files

0.10.0

2 release files

0.9.1

2 release files

0.9.0

2 release files

0.8.0

2 release files

0.7.2

2 release files

0.7.1

2 release files

0.7.0

2 release files

0.6.0

2 release files

0.5.0

2 release files

0.4.1

2 release files

0.4.0

2 release files

0.3.1

2 release files

0.3.0

2 release files

0.2.1

2 release files

0.2.0

2 release files

0.1.1

2 release files

0.1.0

2 release files

Anthropic, PBC Visionary sponsor Bloomberg Visionary sponsor Hudson River Trading Visionary sponsor Meta Visionary sponsor NVIDIA Visionary sponsor Microsoft Sustainability sponsor Depot Continuous Integration AWS Cloud computing and Security Sponsor Datadog Monitoring Fastly CDN Google Download Analytics Sentry Error logging StatusPage Status page