dirigent-examples 0.16.7__tar.gz → 0.17.0__tar.gz

{dirigent_examples-0.16.7 → dirigent_examples-0.17.0}/PKG-INFO

@@ -1,13 +1,13 @@
 Metadata-Version: 2.4
 Name: dirigent-examples
-Version: 0.16.7
+Version: 0.17.0
 Summary: The dirigent example corpus: the shelves of runnable documents, installed.
 License-Expression: LicenseRef-Proprietary
 License-File: LICENSE
 Classifier: Programming Language :: Python :: 3
 Classifier: Programming Language :: Python :: 3.13
-Requires-Dist: dirigent-client==0.16.7
-Requires-Dist: dirigent-plugin==0.16.7
+Requires-Dist: dirigent-client==0.17.0
+Requires-Dist: dirigent-plugin==0.17.0
 Requires-Python: >=3.13
 Description-Content-Type: text/markdown
 

{dirigent_examples-0.16.7 → dirigent_examples-0.17.0}/pyproject.toml

@@ -1,6 +1,6 @@
 [project]
 name = "dirigent-examples"
-version = "0.16.7"
+version = "0.17.0"
 description = "The dirigent example corpus: the shelves of runnable documents, installed."
 readme = "README.md"
 requires-python = ">=3.13"
@@ -11,8 +11,8 @@ classifiers = [
     "Programming Language :: Python :: 3.13",
 ]
 dependencies = [
-    "dirigent-client==0.16.7",
-    "dirigent-plugin==0.16.7",
+    "dirigent-client==0.17.0",
+    "dirigent-plugin==0.17.0",
 ]
 
 [project.entry-points."dirigent.plugins.v1"]

{dirigent_examples-0.16.7 → dirigent_examples-0.17.0}/pyproject.toml.orig

@@ -1,6 +1,6 @@
 [project]
 name = "dirigent-examples"
-version = "0.16.7"
+version = "0.17.0"
 description = "The dirigent example corpus: the shelves of runnable documents, installed."
 readme = "README.md"
 requires-python = ">=3.13"
@@ -12,8 +12,8 @@ classifiers = [
 ]
 dependencies = [
     # The python/ shelf is SDK scripts a reader runs, so the corpus carries the client.
-    "dirigent-client==0.16.7",
-    "dirigent-plugin==0.16.7",
+    "dirigent-client==0.17.0",
+    "dirigent-plugin==0.17.0",
 ]
 
 [project.entry-points."dirigent.plugins.v1"]

{dirigent_examples-0.16.7 → dirigent_examples-0.17.0}/src/dirigent_examples/shelves/recipes/ndjson-to-parquet.yaml

@@ -27,7 +27,7 @@
 # come from the file, so a truncated or half-written object shows up here as a failure
 # instead of downstream tomorrow.
 #
-# convert.arrow ships in dirigent-parquet, on pyarrow, where convert.std deliberately stands
+# convert.arrow ships in dirigent-block-parquet, on pyarrow, where convert.std deliberately stands
 # on the standard library alone. Installing that pack is what puts the block in the catalog,
 # and naming it in requires.blocks is what refuses this document on an instance without it.
 #

{dirigent_examples-0.16.7 → dirigent_examples-0.17.0}/src/dirigent_examples/shelves/s3/README.md

@@ -31,4 +31,4 @@ dg run s3-round-trip -p day=2026-01-01 --watch
 | [s3-copy-and-verify.yaml](s3-copy-and-verify.yaml) | Promote-then-consume: a copy between prefixes, and `storage.exists` standing between the copy and the reader. |
 | [s3-csv-report.yaml](s3-csv-report.yaml) | A report delivered to a bucket: the csv-report chain with the converter's `target` one word away from scratch. |
 | [report-to-s3.yaml](report-to-s3.yaml) | A rendered markdown page delivered to a bucket: `report.render` hands its text on and `storage.write` puts it in the object, content type and all. |
-| [s3-parquet-report.yaml](s3-parquet-report.yaml) | A typed parquet dataset written straight to a bucket, for an analysis to open (needs `dirigent-parquet`). |
+| [s3-parquet-report.yaml](s3-parquet-report.yaml) | A typed parquet dataset written straight to a bucket, for an analysis to open (needs `dirigent-block-parquet`). |

{dirigent_examples-0.16.7 → dirigent_examples-0.17.0}/src/dirigent_examples/shelves/s3/s3-parquet-report.yaml

@@ -6,7 +6,7 @@
 # This is examples/transform/parquet-round-trip.yaml with a real destination. Parquet is
 # the format a downstream analysis actually wants -- columnar, typed, compact -- and what
 # lands in the bucket is a dataset a reader opens with pandas or duckdb, not a csv that
-# lost its numbers on the way out. convert.arrow ships in the dirigent-parquet pack;
+# lost its numbers on the way out. convert.arrow ships in the dirigent-block-parquet pack;
 # installing it puts the block in the catalog.
 #
 #      dg apply examples/s3/s3-parquet-report.yaml

{dirigent_examples-0.16.7 → dirigent_examples-0.17.0}/src/dirigent_examples/shelves/sql/README.md

@@ -14,7 +14,7 @@ dg run --local examples/sql/sql-query-to-storage.yaml
 
 Those two need nothing at all -- no network, no daemon, no server. Each builds a SQLite
 database in the run's own work directory, so the whole example is self-contained. The DuckDB one
-needs the engine (`dirigent-blocks[duckdb]`) and the parquet pack, and nothing else; the last
+needs the engine package (`dirigent-block-duckdb`) and the parquet pack, and nothing else; the last
 names a real PostgreSQL and says so in its own header.
 
 ```bash
@@ -47,6 +47,6 @@ connection names it as `reader@warehouse:5432/warehouse`.
 | --- | --- |
 | [sql-sqlite-roundtrip.yaml](sql-sqlite-roundtrip.yaml) | The family end to end: a table created and filled in one transaction, read back with a bound parameter, and the rows referenced by a downstream step. |
 | [sql-query-to-storage.yaml](sql-query-to-storage.yaml) | Rows into a file: the query hands them on as its output, `storage.write` puts them in an object, and `max_rows` bounds what the step will carry. |
-| [duckdb-parquet-to-report.yaml](duckdb-parquet-to-report.yaml) | The engine that reads files: a parquet artifact queried by DuckDB through a bound `read_parquet(:source)`, and the answer copied out as a csv artifact. Needs the `dirigent-blocks[duckdb]` extra and the parquet pack. |
+| [duckdb-parquet-to-report.yaml](duckdb-parquet-to-report.yaml) | The engine that reads files: a parquet artifact queried by DuckDB through a bound `read_parquet(:source)`, and the answer copied out as a csv artifact. Needs the `dirigent-block-duckdb` engine package and the parquet pack. |
 | [sql-postgres-readonly.yaml](sql-postgres-readonly.yaml) | A referenced PostgreSQL connection with `read_only: true` and its password sealed separately, queried inside the run's window. Validates offline; it cannot run without an instance. |
 | [warehouse.sql](warehouse.sql) | Not a pipeline: the roles and the one table the compose stack's warehouse is seeded with, mounted by `infra/compose.sql.yaml` |

{dirigent_examples-0.16.7 → dirigent_examples-0.17.0}/src/dirigent_examples/shelves/sql/duckdb-parquet-to-report.yaml

@@ -1,8 +1,8 @@
 # SQL over files: DuckDB reads a parquet artifact and writes a csv one.
 #
 # NEEDS NOTHING BUT THE ENGINE: no network, no daemon, no server, no allowlist. It does need
-# duckdb on the worker, which is the dirigent-blocks[duckdb] extra, and convert.arrow, which
-# is the dirigent-parquet pack.
+# duckdb on the worker, which is the dirigent-block-duckdb package, and convert.arrow, which
+# is the dirigent-block-parquet pack.
 #   dg run --local examples/sql/duckdb-parquet-to-report.yaml --keep
 # docs/sql.md is the family's home.
 #

{dirigent_examples-0.16.7 → dirigent_examples-0.17.0}/src/dirigent_examples/shelves/transform/README.md

@@ -28,7 +28,7 @@ dg run --local examples/transform/jq-reshape.yaml
 | [ndjson-round-trip.yaml](ndjson-round-trip.yaml) | ndjson: a JSON array re-spelled one record per line, and read back. |
 | [yaml-config-to-json.yaml](yaml-config-to-json.yaml) | yaml: one document is one value, so a config becomes the object it describes, and comes back a document. |
 | [xml-feed-to-ndjson.yaml](xml-feed-to-ndjson.yaml) | xml: a feed's elements as one record per line, the mapping that makes attributes and children keys, and the whole document as one object. |
-| [parquet-round-trip.yaml](parquet-round-trip.yaml) | Records to parquet and back, the types surviving where csv would flatten them to strings (needs `dirigent-parquet`). |
+| [parquet-round-trip.yaml](parquet-round-trip.yaml) | Records to parquet and back, the types surviving where csv would flatten them to strings (needs `dirigent-block-parquet`). |
 
 Every program on this shelf is reference-free, so jq compiles them when the document is
 applied and a syntax error is an issue beside every other one the document has. That is why

{dirigent_examples-0.16.7 → dirigent_examples-0.17.0}/src/dirigent_examples/shelves/transform/parquet-round-trip.yaml

@@ -11,7 +11,7 @@
 # the records in storage to begin with, and storage.read the hop that brings the result
 # back where a later step, or a person reading the run, can see it.
 #
-# convert.arrow ships in the dirigent-parquet pack; installing it is what puts the block in
+# convert.arrow ships in the dirigent-block-parquet pack; installing it is what puts the block in
 # the catalog.
 #
 #   dg run --local examples/transform/parquet-round-trip.yaml --keep