Fluksio/app
0
0
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity

Export FLOWS and build from the top-level fluksio package

Browse Source 
A test of the declarations had to import them from fluksio.sdk while the
guide teaches `from fluksio import ...`. The worker's inert module gets the
same two names so a module importing them still loads inside a node.

Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_01QgG6TJw5qBZzaLghQSRVrq
This commit is contained in:
stroblme
2026-09-16 16:44:47 +02:00
co-authored by Claude Opus 5
parent 96fe2e0bc3
commit 3dc43be6d0
4 changed files with 29 additions and 2 deletions
Download Patch File Download Diff File Expand all files Collapse all files
docs/getting-started/data-science.md
+4
View File
@@ -415,6 +415,10 @@ finetune = Flow(
different message, keyword arguments override settings, and `id=` tells two
uses of one function apart. `train` above is unaffected by any of it.
A test can check the declarations without an engine. Importing the module
registers its flows in `fluksio.FLOWS`, and `fluksio.build(flow)` returns the
document `sync` would upload, refusing what the engine would refuse.
## Sync it
```sh