nodebpy 520.23.0__tar.gz → 520.24.0__tar.gz

{nodebpy-520.23.0 → nodebpy-520.24.0}/PKG-INFO

@@ -1,6 +1,6 @@
 Metadata-Version: 2.3
 Name: nodebpy
-Version: 520.23.0
+Version: 520.24.0
 Summary: Build nodes trees in Blender more elegantly with code
 Author: Brady Johnston
 Author-email: Brady Johnston <brady.johnston@me.com>

{nodebpy-520.23.0 → nodebpy-520.24.0}/pyproject.toml

@@ -1,6 +1,6 @@
 [project]
 name = "nodebpy"
-version = "520.23.0"
+version = "520.24.0"
 description = "Build nodes trees in Blender more elegantly with code"
 readme = "README.md"
 authors = [

{nodebpy-520.23.0 → nodebpy-520.24.0}/src/nodebpy/export/codegen.py

@@ -946,9 +946,20 @@ def _ordering_edges(node_tree, keep_reroutes: bool = False):
     """(from, to) node pairs that must hold in emission order: effective
     links (canonical order, reroutes collapsed) plus a synthetic edge from
     each zone input node to its paired output, so the zone wrapper is
-    declared before the output side is emitted."""
+    declared before the output side is emitted.
+
+    Links from Group Input nodes impose no order: they render as interface
+    references (bound in the interface block, before any node emits), and
+    a tree holding several instances (split inputs) must not let the
+    instances' names gate their consumers' readiness in the lexicographic
+    topological sort — which instance feeds a consumer follows link
+    creation order, so emission order would depend on the previous
+    emission and oscillate across dump → build round trips."""
     for link in _effective_links(node_tree, keep_reroutes):
-        if link.from_node != link.to_node:
+        if (
+            link.from_node != link.to_node
+            and link.from_node.bl_idname != "NodeGroupInput"
+        ):
             yield link.from_node, link.to_node
     for node in node_tree.nodes:
         paired = getattr(node, "paired_output", None)