duckdb-kql 0.0.1.dev1__tar.gz → 0.0.1.dev2__tar.gz

{duckdb_kql-0.0.1.dev1 → duckdb_kql-0.0.1.dev2}/CONTRIBUTING.md

@@ -24,7 +24,7 @@ Docker, DuckDB and the emulator yourself.
 Before opening a pull request:
 
 ```bash
-ruff check src tools tests
+ruff check src tools tests demo
 mypy
 pytest
 ```
@@ -87,6 +87,7 @@ report waiting to be filed against someone else's report.
 | Links in the docs resolve | Including the absolute ones the README uses for PyPI. |
 | A consumer's type checker sees real types | The package ships `py.typed`, so `Any` in a public signature is a promise broken silently. `tests/test_typing.py` checks from the outside; `mypy` alone cannot. |
 | The committed parser matches `grammar/Kql.g4` | The generated parser is committed so installs need no Java. |
+| The demo notebook still executes | `demo/` ships with its outputs, so a broken demo keeps looking authoritative. |
 
 ## The emulator
 
@@ -155,6 +156,15 @@ The whole procedure:
 1. Go to **Releases → Draft a new release**, create the tag `vX.Y.Z` on `main`,
    click **Generate release notes**, and publish.
 
+**The tag is used verbatim**, so any PEP 440 version works — `v0.2.0`,
+`v0.2.0rc1`, `v0.0.1.dev1`. This is `version_scheme = "only-version"` in
+`pyproject.toml`, and it is deliberate: `setuptools_scm`'s default invents a
+version for untagged commits by guessing the next release and appending
+`.dev<distance>`, which makes a tag that already ends in `.devN` unbuildable and
+breaks *every commit after it*. Taking the tag as written avoids the guess
+entirely; untagged builds are told apart by a local segment naming the commit
+(`0.0.1.dev1+gfe285ea`) rather than by counting commits.
+
 That is it. The release workflow builds the sdist and wheel, verifies the built
 version equals the tag, smoke-tests the wheel in a clean environment, uploads to
 PyPI via [Trusted Publishing][oidc], and attaches the artifacts to the release.

{duckdb_kql-0.0.1.dev1 → duckdb_kql-0.0.1.dev2}/PKG-INFO

@@ -1,6 +1,6 @@
-Metadata-Version: 2.4
+Metadata-Version: 2.5
 Name: duckdb-kql
-Version: 0.0.1.dev1
+Version: 0.0.1.dev2
 Summary: Run Kusto KQL queries on DuckDB, from Python
 Project-URL: Homepage, https://github.com/mmaitre314/duckdb-kql
 Project-URL: Documentation, https://github.com/mmaitre314/duckdb-kql/blob/main/docs/getting-started.md
@@ -58,7 +58,10 @@ Provides-Extra: arrow
 Requires-Dist: pyarrow; extra == 'arrow'
 Provides-Extra: dev
 Requires-Dist: duckdb>=0.10; extra == 'dev'
+Requires-Dist: ipykernel; extra == 'dev'
 Requires-Dist: mypy>=1.11; extra == 'dev'
+Requires-Dist: nbclient; extra == 'dev'
+Requires-Dist: nbformat; extra == 'dev'
 Requires-Dist: pandas; extra == 'dev'
 Requires-Dist: pandas-stubs; extra == 'dev'
 Requires-Dist: pyarrow; extra == 'dev'
@@ -163,7 +166,7 @@ runs without a database.
 import duckdb_kql
 
 con = duckdb_kql.connect("analytics.duckdb")   # duckdb.connect + TimeZone=UTC
-rel = duckdb_kql.sql(con, "StormEvents | summarize n = count() by State")
+rel = duckdb_kql.kql(con, "StormEvents | summarize n = count() by State")
 rel.fetchall()
 ```
 
@@ -198,7 +201,7 @@ values; they are bound as values, so the generated SQL contains no
 caller-controlled text at all.
 
 ```python
-duckdb_kql.sql(con, """
+duckdb_kql.kql(con, """
     declare query_parameters(state:string);
     StormEvents | where State == state
 """, {"state": user_input})     # safe whatever user_input contains
@@ -256,6 +259,7 @@ approximation.
 | [`docs/m0-grammar-spike.md`](https://github.com/mmaitre314/duckdb-kql/blob/main/docs/m0-grammar-spike.md) | Grammar viability result |
 | [`docs/frequency-scan-results.md`](https://github.com/mmaitre314/duckdb-kql/blob/main/docs/frequency-scan-results.md) | What KQL constructs actually get used |
 | [`docs/licensing.md`](https://github.com/mmaitre314/duckdb-kql/blob/main/docs/licensing.md) | Third-party licensing review |
+| [demo/](https://github.com/mmaitre314/duckdb-kql/blob/main/demo/duckdb-kql-demo.ipynb) | Notebook tour of all three layers, with outputs |
 | [CONTRIBUTING.md](https://github.com/mmaitre314/duckdb-kql/blob/main/CONTRIBUTING.md) | How to add a mapping, and when not to |
 | [SECURITY.md](https://github.com/mmaitre314/duckdb-kql/blob/main/SECURITY.md) | Reporting vulnerabilities; what is in scope |
 | [Releases](https://github.com/mmaitre314/duckdb-kql/releases) | What changed, and when |

{duckdb_kql-0.0.1.dev1 → duckdb_kql-0.0.1.dev2}/README.md

@@ -85,7 +85,7 @@ runs without a database.
 import duckdb_kql
 
 con = duckdb_kql.connect("analytics.duckdb")   # duckdb.connect + TimeZone=UTC
-rel = duckdb_kql.sql(con, "StormEvents | summarize n = count() by State")
+rel = duckdb_kql.kql(con, "StormEvents | summarize n = count() by State")
 rel.fetchall()
 ```
 
@@ -120,7 +120,7 @@ values; they are bound as values, so the generated SQL contains no
 caller-controlled text at all.
 
 ```python
-duckdb_kql.sql(con, """
+duckdb_kql.kql(con, """
     declare query_parameters(state:string);
     StormEvents | where State == state
 """, {"state": user_input})     # safe whatever user_input contains
@@ -178,6 +178,7 @@ approximation.
 | [`docs/m0-grammar-spike.md`](https://github.com/mmaitre314/duckdb-kql/blob/main/docs/m0-grammar-spike.md) | Grammar viability result |
 | [`docs/frequency-scan-results.md`](https://github.com/mmaitre314/duckdb-kql/blob/main/docs/frequency-scan-results.md) | What KQL constructs actually get used |
 | [`docs/licensing.md`](https://github.com/mmaitre314/duckdb-kql/blob/main/docs/licensing.md) | Third-party licensing review |
+| [demo/](https://github.com/mmaitre314/duckdb-kql/blob/main/demo/duckdb-kql-demo.ipynb) | Notebook tour of all three layers, with outputs |
 | [CONTRIBUTING.md](https://github.com/mmaitre314/duckdb-kql/blob/main/CONTRIBUTING.md) | How to add a mapping, and when not to |
 | [SECURITY.md](https://github.com/mmaitre314/duckdb-kql/blob/main/SECURITY.md) | Reporting vulnerabilities; what is in scope |
 | [Releases](https://github.com/mmaitre314/duckdb-kql/releases) | What changed, and when |