labcode 0.10.1__tar.gz → 0.10.3__tar.gz

{labcode-0.10.1 → labcode-0.10.3}/CHANGELOG.md

@@ -6,6 +6,45 @@ specification the section numbers refer to is [`docs/SPECIFICATIONS.md`](docs/SP
 Releases before 0.9.0 are described in the messages of their `Release vX.Y.Z` commits
 (`git log --grep '^Release v'`).
 
+## 0.10.3 — 2026-10-08
+
+No code changes; the siblings move.
+
+### Added
+
+- **A `branch` runs where the boundary decides its arm.** A branch whose condition is
+  an entry input -- a flag, or one flag per element inside a `map` -- runs the arm the
+  flag picks: the runner states each arm in the document's `expansion.arms`
+  (ofplang-schedule SPEC §6.13) and the scheduler expands the branch with it
+  (ofplang-schedule 0.15, ofplang-run 0.15). A flag left out is `false` and reported
+  (`entry_input_defaulted`). A branch whose condition is produced during the run is
+  refused before anything runs (`branch_arm_unknown`).
+
+Requires ofplang-schedule 0.15 and ofplang-run 0.15 (ofplang-validate 0.4.1 as before).
+
+## 0.10.2 — 2026-10-07
+
+No code changes; the siblings move.
+
+### Added
+
+- **A `map` / `fold` over a list of values runs.** `lc run` is given a list of labels,
+  volumes or the like and makes one invocation per element: the runner counts each
+  list and states its length in the document's `expansion` (ofplang-schedule SPEC
+  §6.13), and the scheduler expands by it (ofplang-schedule 0.14, ofplang-run 0.14).
+  Until now such a workflow was refused (`array_length_unknown`).
+
+### Changed — may need your attention
+
+- **A list zipped with an Array of plates of another length is refused before the run
+  starts** (`each_length_mismatch`), where it used to stop that job at its first check.
+- **A structured node's `outputs` is checked as the specification says** (ofplang-validate
+  0.4.1). An entry with no `mode` is `missing_required_key`, and a reference to an output
+  the node does not expose -- one its `outputs` drops, or one dropped by default -- is
+  `output_not_exposed`. Both passed validation before.
+
+Requires ofplang-validate 0.4.1, ofplang-schedule 0.14.1 and ofplang-run 0.14.1.
+
 ## 0.10.1 — 2026-10-07
 
 labcode follows specification revision 0.5. No code changes; the siblings move.

{labcode-0.10.1 → labcode-0.10.3}/PKG-INFO

@@ -1,6 +1,6 @@
 Metadata-Version: 2.4
 Name: labcode
-Version: 0.10.1
+Version: 0.10.3
 Summary: labcode -- a dialect wrapper over the Object-Flow Programming Language toolchain
 Author-email: Kazunari Kaizu <kwaizu@gmail.com>
 License-Expression: MIT
@@ -20,9 +20,9 @@ Classifier: Typing :: Typed
 Requires-Python: >=3.10
 Description-Content-Type: text/markdown
 License-File: LICENSE
-Requires-Dist: ofplang-validate<0.5,>=0.4
-Requires-Dist: ofplang-schedule<0.14,>=0.13.1
-Requires-Dist: ofplang-run<0.14,>=0.13.1
+Requires-Dist: ofplang-validate<0.5,>=0.4.1
+Requires-Dist: ofplang-schedule<0.16,>=0.15
+Requires-Dist: ofplang-run<0.16,>=0.15
 Provides-Extra: test
 Requires-Dist: pytest>=7.0; extra == "test"
 Requires-Dist: opentelemetry-sdk>=1.20; extra == "test"

{labcode-0.10.1 → labcode-0.10.3}/labcode.egg-info/PKG-INFO

@@ -1,6 +1,6 @@
 Metadata-Version: 2.4
 Name: labcode
-Version: 0.10.1
+Version: 0.10.3
 Summary: labcode -- a dialect wrapper over the Object-Flow Programming Language toolchain
 Author-email: Kazunari Kaizu <kwaizu@gmail.com>
 License-Expression: MIT
@@ -20,9 +20,9 @@ Classifier: Typing :: Typed
 Requires-Python: >=3.10
 Description-Content-Type: text/markdown
 License-File: LICENSE
-Requires-Dist: ofplang-validate<0.5,>=0.4
-Requires-Dist: ofplang-schedule<0.14,>=0.13.1
-Requires-Dist: ofplang-run<0.14,>=0.13.1
+Requires-Dist: ofplang-validate<0.5,>=0.4.1
+Requires-Dist: ofplang-schedule<0.16,>=0.15
+Requires-Dist: ofplang-run<0.16,>=0.15
 Provides-Extra: test
 Requires-Dist: pytest>=7.0; extra == "test"
 Requires-Dist: opentelemetry-sdk>=1.20; extra == "test"

{labcode-0.10.1 → labcode-0.10.3}/labcode.egg-info/requires.txt

@@ -1,6 +1,6 @@
-ofplang-validate<0.5,>=0.4
-ofplang-schedule<0.14,>=0.13.1
-ofplang-run<0.14,>=0.13.1
+ofplang-validate<0.5,>=0.4.1
+ofplang-schedule<0.16,>=0.15
+ofplang-run<0.16,>=0.15
 
 [dev]
 pytest>=7.0

labcode-0.10.3/labcode.egg-info/scm_version.json

@@ -0,0 +1,8 @@
+{
+  "tag": "0.10.3",
+  "distance": 0,
+  "node": "g748b5b84ca5df86201d3cf46406dd544cb84a4ab",
+  "dirty": false,
+  "branch": "HEAD",
+  "node_date": "2026-10-08"
+}

{labcode-0.10.1 → labcode-0.10.3}/pyproject.toml

@@ -62,8 +62,20 @@ classifiers = [
 # every real-lab example already happens on it, and run's own floor requires it anyway
 # (an older scheduler reports a running refill free before it is).
 #
-# `ofplang-validate>=0.4`, `ofplang-schedule>=0.13.1` and `ofplang-run>=0.13.1` are
-# required together: they implement specification revision 0.5, and `lc` validates at its
+# `ofplang-schedule>=0.15` and `ofplang-run>=0.15` move together: a `branch` whose arm
+# the boundary decides runs from these (the run states each arm as the document's
+# `expansion.arms`, the scheduler expands by it), and run 0.15 needs schedule 0.15.
+#
+# `ofplang-validate>=0.4.1`, `ofplang-schedule>=0.14.1` and `ofplang-run>=0.14.1` were
+# required together. A `map` / `fold` over a list of values is planned and run from
+# these (the run states each list's length as the document's `expansion`, the scheduler
+# expands by it), and the front door and the scheduler's reader agree again on what a
+# structured node's `outputs` may say: an entry with no mode, and a reference to an
+# output the node does not expose, are refused by both (validate 0.4.1), where before
+# validate passed what the reader refused.
+#
+# The `ofplang-validate>=0.4`, `ofplang-schedule>=0.13.1` and `ofplang-run>=0.13.1`
+# floors they replace were required together: they implement specification revision 0.5, and `lc` validates at its
 # front door with the one validate and plans and runs with the others, so the three have
 # to agree on what is valid. Under validate 0.3 a composite could leave an output
 # unreturned that the scheduler's reader now refuses, and a `scheduling` section passed
@@ -76,7 +88,7 @@ classifiers = [
 # labcode keys each plate's `_id` by its element. `RunResult.run_warnings`, which `lc run`
 # fills with what labcode defaulted, is new in run 0.13 too.
 #
-# 🔴 The schedule `<0.14` bound is a bound, not a floor: 0.10 refuses two jobs binding one
+# 🔴 The schedule upper bound is a bound, not a floor: 0.10 refuses two jobs binding one
 # boundary spot where it used to warn, and 0.12 refuses a plan it can show has no
 # schedule before the solve instead of returning `unknown`. Both change what happens to
 # a document this package hands over rather than anything it calls.
@@ -95,9 +107,9 @@ dependencies = [
 # would pick up the next such sibling and start refusing its own examples. The
 # bounds cannot protect what is already on PyPI without one, which is why they go
 # in now rather than at the first breakage.
-    "ofplang-validate>=0.4,<0.5",
-    "ofplang-schedule>=0.13.1,<0.14",
-    "ofplang-run>=0.13.1,<0.14",
+    "ofplang-validate>=0.4.1,<0.5",
+    "ofplang-schedule>=0.15,<0.16",
+    "ofplang-run>=0.15,<0.16",
 ]
 
 [project.urls]

labcode-0.10.1/labcode.egg-info/scm_version.json

@@ -1,8 +0,0 @@
-{
-  "tag": "0.10.1",
-  "distance": 0,
-  "node": "g1787216e03cd07ec2fe1ed38539ba7006be08494",
-  "dirty": false,
-  "branch": "HEAD",
-  "node_date": "2026-10-06"
-}