pulze-renderflow 2.0.7__tar.gz → 2.0.8__tar.gz

{pulze_renderflow-2.0.7 → pulze_renderflow-2.0.8}/PKG-INFO

@@ -1,6 +1,6 @@
 Metadata-Version: 2.5
 Name: pulze-renderflow
-Version: 2.0.7
+Version: 2.0.8
 Summary: Official RenderFlow API client for Python
 Project-URL: Homepage, https://pulze.io/products/renderflow
 Author-email: Pulze <support@pulze.io>
@@ -18,7 +18,7 @@ Classifier: Programming Language :: Python :: 3.13
 Requires-Python: >=3.10
 Description-Content-Type: text/markdown
 
-# renderflow
+# pulze-renderflow
 
 Official Python client for the [RenderFlow](https://pulze.io/products/renderflow) API.
 
@@ -55,7 +55,7 @@ Operations are grouped by tag and named after the API document's `operationId`,
 reads the same here, in the TypeScript SDK, in `rfcli` and in the MCP tools:
 
 ```python
-farm.tags()                 # every group: jobs, nodes, pools, schedule, ...
+farm.tags()                 # every group: jobs, nodes, pools, schedule, render_licenses, ...
 dir(farm.jobs)              # every operation in one: get_jobs, create_job, stop_job, ...
 help(farm.jobs.get_jobs)    # the operation's own documentation, generated from the document
 ```
@@ -73,10 +73,14 @@ help(farm.jobs.get_jobs)    # the operation's own documentation, generated from
 A recipe — `type` plus a file and the flat per-DCC fields — is the short way in; the service
 expands it into the step tree:
 
+Every recipe requires `type`, `file` and `host` — `host` is which application renders it, and only
+its `id` is mandatory:
+
 ```python
 job = farm.jobs.create_job(body={
     "type": "blender.render",
     "file": "//share/scenes/shot_010.blend",
+    "host": {"id": "blender", "version": "4.5"},
     "frame": "1-100",
     "pool_id": "...",
 })
@@ -96,7 +100,7 @@ reads them from `models.pyi` — autocomplete and type checking with nothing to
 ```python
 from renderflow.models import MayaRenderRecipe
 
-recipe: MayaRenderRecipe = {"type": "maya.render", "file": "//share/scenes/hero.mb", "host": {"name": "maya"}}
+recipe: MayaRenderRecipe = {"type": "maya.render", "file": "//share/scenes/hero.mb", "host": {"id": "maya", "version": "2026"}}
 farm.jobs.create_job(body=recipe)
 ```
 

{pulze_renderflow-2.0.7 → pulze_renderflow-2.0.8}/README.md

@@ -1,4 +1,4 @@
-# renderflow
+# pulze-renderflow
 
 Official Python client for the [RenderFlow](https://pulze.io/products/renderflow) API.
 
@@ -35,7 +35,7 @@ Operations are grouped by tag and named after the API document's `operationId`,
 reads the same here, in the TypeScript SDK, in `rfcli` and in the MCP tools:
 
 ```python
-farm.tags()                 # every group: jobs, nodes, pools, schedule, ...
+farm.tags()                 # every group: jobs, nodes, pools, schedule, render_licenses, ...
 dir(farm.jobs)              # every operation in one: get_jobs, create_job, stop_job, ...
 help(farm.jobs.get_jobs)    # the operation's own documentation, generated from the document
 ```
@@ -53,10 +53,14 @@ help(farm.jobs.get_jobs)    # the operation's own documentation, generated from
 A recipe — `type` plus a file and the flat per-DCC fields — is the short way in; the service
 expands it into the step tree:
 
+Every recipe requires `type`, `file` and `host` — `host` is which application renders it, and only
+its `id` is mandatory:
+
 ```python
 job = farm.jobs.create_job(body={
     "type": "blender.render",
     "file": "//share/scenes/shot_010.blend",
+    "host": {"id": "blender", "version": "4.5"},
     "frame": "1-100",
     "pool_id": "...",
 })
@@ -76,7 +80,7 @@ reads them from `models.pyi` — autocomplete and type checking with nothing to
 ```python
 from renderflow.models import MayaRenderRecipe
 
-recipe: MayaRenderRecipe = {"type": "maya.render", "file": "//share/scenes/hero.mb", "host": {"name": "maya"}}
+recipe: MayaRenderRecipe = {"type": "maya.render", "file": "//share/scenes/hero.mb", "host": {"id": "maya", "version": "2026"}}
 farm.jobs.create_job(body=recipe)
 ```
 

{pulze_renderflow-2.0.7 → pulze_renderflow-2.0.8}/pyproject.toml

@@ -4,7 +4,7 @@ build-backend = "hatchling.build"
 
 [project]
 name = "pulze-renderflow"
-version = "2.0.7"
+version = "2.0.8"
 description = "Official RenderFlow API client for Python"
 readme = "README.md"
 license = "MIT"

{pulze_renderflow-2.0.7 → pulze_renderflow-2.0.8}/renderflow/wire.py

@@ -26,8 +26,12 @@ _index: Optional[Dict[str, Dict[str, "Operation"]]] = None
 
 
 def snake(name: str) -> str:
-    """`getJobs` → `get_jobs`, `UserGroups` → `user_groups` — the spelling everything else uses."""
-    return re.sub(r"(?<=[a-z0-9])([A-Z])", r"_\1", name).lower()
+    """`getJobs` → `get_jobs`, `UserGroups` → `user_groups` — the spelling everything else uses.
+
+    Spaces and dashes separate too: a tag is written for humans (`Render licenses`), and whatever
+    it says has to come out as something an attribute can be named.
+    """
+    return re.sub(r"[\s-]+", "_", re.sub(r"(?<=[a-z0-9])([A-Z])", r"_\1", name).strip()).lower()
 
 
 class Operation: