dactopus 0.2.0__tar.gz → 0.2.1__tar.gz

This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.
Files changed (51) hide show
  1. {dactopus-0.2.0 → dactopus-0.2.1}/.github/workflows/ci.yml +1 -1
  2. {dactopus-0.2.0 → dactopus-0.2.1}/AGENTS.md +6 -2
  3. {dactopus-0.2.0 → dactopus-0.2.1}/CHANGELOG.md +16 -1
  4. {dactopus-0.2.0 → dactopus-0.2.1}/CONTRIBUTING.md +2 -2
  5. {dactopus-0.2.0 → dactopus-0.2.1}/PKG-INFO +12 -5
  6. {dactopus-0.2.0 → dactopus-0.2.1}/README.md +10 -3
  7. {dactopus-0.2.0 → dactopus-0.2.1}/docs/design.md +28 -0
  8. {dactopus-0.2.0 → dactopus-0.2.1}/pyproject.toml +3 -2
  9. {dactopus-0.2.0 → dactopus-0.2.1}/src/dactopus/cli.py +14 -0
  10. {dactopus-0.2.0 → dactopus-0.2.1}/tests/test_cli.py +9 -0
  11. {dactopus-0.2.0 → dactopus-0.2.1}/uv.lock +6 -503
  12. {dactopus-0.2.0 → dactopus-0.2.1}/.github/dependabot.yml +0 -0
  13. {dactopus-0.2.0 → dactopus-0.2.1}/.github/workflows/publish.yml +0 -0
  14. {dactopus-0.2.0 → dactopus-0.2.1}/.gitignore +0 -0
  15. {dactopus-0.2.0 → dactopus-0.2.1}/CLAUDE.md +0 -0
  16. {dactopus-0.2.0 → dactopus-0.2.1}/LICENSE +0 -0
  17. {dactopus-0.2.0 → dactopus-0.2.1}/src/dactopus/__init__.py +0 -0
  18. {dactopus-0.2.0 → dactopus-0.2.1}/src/dactopus/build.py +0 -0
  19. {dactopus-0.2.0 → dactopus-0.2.1}/src/dactopus/checks.py +0 -0
  20. {dactopus-0.2.0 → dactopus-0.2.1}/src/dactopus/clickhouse.py +0 -0
  21. {dactopus-0.2.0 → dactopus-0.2.1}/src/dactopus/config.py +0 -0
  22. {dactopus-0.2.0 → dactopus-0.2.1}/src/dactopus/ga4.py +0 -0
  23. {dactopus-0.2.0 → dactopus-0.2.1}/src/dactopus/library.py +0 -0
  24. {dactopus-0.2.0 → dactopus-0.2.1}/src/dactopus/report.py +0 -0
  25. {dactopus-0.2.0 → dactopus-0.2.1}/src/dactopus/serve.py +0 -0
  26. {dactopus-0.2.0 → dactopus-0.2.1}/src/dactopus/shopify.py +0 -0
  27. {dactopus-0.2.0 → dactopus-0.2.1}/tests/conftest.py +0 -0
  28. {dactopus-0.2.0 → dactopus-0.2.1}/tests/fixtures/dbt/shopify/manifest.json +0 -0
  29. {dactopus-0.2.0 → dactopus-0.2.1}/tests/fixtures/dbt/shopify/run_results_build_error.json +0 -0
  30. {dactopus-0.2.0 → dactopus-0.2.1}/tests/fixtures/dbt/shopify/run_results_build_pass.json +0 -0
  31. {dactopus-0.2.0 → dactopus-0.2.1}/tests/fixtures/dbt/shopify/run_results_build_schema_change.json +0 -0
  32. {dactopus-0.2.0 → dactopus-0.2.1}/tests/fixtures/dbt/shopify/run_results_build_skipped.json +0 -0
  33. {dactopus-0.2.0 → dactopus-0.2.1}/tests/fixtures/dbt/shopify/run_results_test_fail.json +0 -0
  34. {dactopus-0.2.0 → dactopus-0.2.1}/tests/fixtures/dbt/shopify/sources_error.json +0 -0
  35. {dactopus-0.2.0 → dactopus-0.2.1}/tests/fixtures/dbt/shopify/sources_pass.json +0 -0
  36. {dactopus-0.2.0 → dactopus-0.2.1}/tests/fixtures/dbt/shopify/sources_stale.json +0 -0
  37. {dactopus-0.2.0 → dactopus-0.2.1}/tests/fixtures/ga4_export_schema.arrow +0 -0
  38. {dactopus-0.2.0 → dactopus-0.2.1}/tests/fixtures/library/sources/broken/deployment.yml +0 -0
  39. {dactopus-0.2.0 → dactopus-0.2.1}/tests/fixtures/library/sources/ga4/deployment.yml +0 -0
  40. {dactopus-0.2.0 → dactopus-0.2.1}/tests/fixtures/library/sources/shopify/deployment.yml +0 -0
  41. {dactopus-0.2.0 → dactopus-0.2.1}/tests/fixtures/shopify_order_imported.json +0 -0
  42. {dactopus-0.2.0 → dactopus-0.2.1}/tests/fixtures/shopify_orders.json +0 -0
  43. {dactopus-0.2.0 → dactopus-0.2.1}/tests/fixtures/shopify_products.json +0 -0
  44. {dactopus-0.2.0 → dactopus-0.2.1}/tests/test_build.py +0 -0
  45. {dactopus-0.2.0 → dactopus-0.2.1}/tests/test_checks.py +0 -0
  46. {dactopus-0.2.0 → dactopus-0.2.1}/tests/test_config.py +0 -0
  47. {dactopus-0.2.0 → dactopus-0.2.1}/tests/test_ga4.py +0 -0
  48. {dactopus-0.2.0 → dactopus-0.2.1}/tests/test_library.py +0 -0
  49. {dactopus-0.2.0 → dactopus-0.2.1}/tests/test_report.py +0 -0
  50. {dactopus-0.2.0 → dactopus-0.2.1}/tests/test_serve.py +0 -0
  51. {dactopus-0.2.0 → dactopus-0.2.1}/tests/test_shopify.py +0 -0
@@ -31,7 +31,7 @@ jobs:
31
31
  - run: uvx twine check --strict dist/* # the README is the PyPI page
32
32
  - name: The wheel works on its own, outside the checkout
33
33
  run: |
34
- uv venv "$RUNNER_TEMP/wheel"
34
+ uv venv --python 3.13 "$RUNNER_TEMP/wheel"
35
35
  uv pip install --python "$RUNNER_TEMP/wheel" "$(ls dist/*.whl)"
36
36
  cd "$RUNNER_TEMP" && wheel/bin/dactopus init --config sample.yaml
37
37
  wheel/bin/python -c "import dactopus.serve, dactopus_ossie_clickhouse.mcp_server"
@@ -58,7 +58,7 @@ Out of scope, do not build:
58
58
  reads several files as one model; the runner only lists them.
59
59
  - Migration from a client's dbt or Looker.
60
60
  - An installer, a Docker image, a single-file build. Installation is
61
- `uv`, as for the executor.
61
+ `uv tool install` from PyPI.
62
62
  - Placeholders or stubs for any of the above.
63
63
 
64
64
  ## Design principles
@@ -95,7 +95,11 @@ Out of scope, do not build:
95
95
 
96
96
  ## Stack
97
97
 
98
- Python 3.11+, managed with uv. The parts that constrain code:
98
+ Python 3.11 to 3.13, managed with uv: dbt-core 1.11 does not start on
99
+ 3.14, and dbt-core 1.12, which does, cannot be installed without access
100
+ to GitHub ([docs/design.md](docs/design.md)). Every dependency comes from
101
+ PyPI: PyPI refuses a package that depends on a git reference, so one
102
+ breaks the next release. The parts that constrain code:
99
103
 
100
104
  - **dbt v1**: `dbt-core` 1.11 with `dbt-clickhouse`. Packages are dbt
101
105
  projects and also run on dbt v2, but its ClickHouse adapter is in beta
@@ -7,6 +7,20 @@ a minor release may change the command line and the configuration file.
7
7
 
8
8
  ## [Unreleased]
9
9
 
10
+ ## [0.2.1] - 2026-11-01
11
+
12
+ ### Fixed
13
+
14
+ - Python 3.11 to 3.13. On 3.14 the install succeeded and the first
15
+ `dactopus run` failed inside dbt: dbt-core 1.11 does not start there.
16
+ The README installs with `uv tool install --python 3.13 dactopus`;
17
+ every command refuses 3.14 and gives that command with `--force`;
18
+ `requires-python` is `>=3.11,<3.14`, which pip enforces and uv does
19
+ not.
20
+ - The README says how to update (`uv tool upgrade dactopus`) and how an
21
+ installation of 0.1.0 or 0.1.1 from GitHub moves to PyPI
22
+ (`uv tool install --force --python 3.13 dactopus`).
23
+
10
24
  ## [0.2.0] - 2026-11-01
11
25
 
12
26
  ### Added
@@ -133,7 +147,8 @@ The first release, a prototype.
133
147
  with the version to set. The vars of a package are checked against
134
148
  the file before any connection.
135
149
 
136
- [Unreleased]: https://github.com/Dactopus/dactopus/compare/v0.2.0...HEAD
150
+ [Unreleased]: https://github.com/Dactopus/dactopus/compare/v0.2.1...HEAD
151
+ [0.2.1]: https://github.com/Dactopus/dactopus/releases/tag/v0.2.1
137
152
  [0.2.0]: https://github.com/Dactopus/dactopus/releases/tag/v0.2.0
138
153
  [0.1.1]: https://github.com/Dactopus/dactopus/releases/tag/v0.1.1
139
154
  [0.1.0]: https://github.com/Dactopus/dactopus/releases/tag/v0.1.0
@@ -5,7 +5,7 @@ repository is in English: code, comments, commit messages, issues.
5
5
 
6
6
  ## Setup
7
7
 
8
- Python 3.11+ and [uv](https://docs.astral.sh/uv/).
8
+ Python 3.11 to 3.13 and [uv](https://docs.astral.sh/uv/).
9
9
 
10
10
  ```bash
11
11
  git clone https://github.com/Dactopus/dactopus
@@ -61,7 +61,7 @@ GitHub release is titled `X.Y.Z`.
61
61
  git switch main && git pull --ff-only
62
62
  gh workflow run publish.yml --ref main # step 4, TestPyPI
63
63
  uvx pip download --no-deps --index-url https://test.pypi.org/simple/ -d testpypi "dactopus==X.Y.Z.devN"
64
- uv tool install --force testpypi/dactopus-X.Y.Z.devN-py3-none-any.whl # dependencies from PyPI
64
+ uv tool install --force --python 3.13 testpypi/dactopus-X.Y.Z.devN-py3-none-any.whl # dependencies from PyPI
65
65
  git tag -a vX.Y.Z -m "dactopus X.Y.Z" && git push origin vX.Y.Z
66
66
  gh release create vX.Y.Z --title X.Y.Z --notes-file notes.md # publishes to PyPI
67
67
  ```
@@ -1,6 +1,6 @@
1
1
  Metadata-Version: 2.5
2
2
  Name: dactopus
3
- Version: 0.2.0
3
+ Version: 0.2.1
4
4
  Summary: Runner of Dactopus: loads sources into ClickHouse, builds the canonical tables, runs checks, serves the models over MCP
5
5
  Project-URL: Homepage, https://github.com/Dactopus/dactopus
6
6
  Project-URL: Issues, https://github.com/Dactopus/dactopus/issues
@@ -16,7 +16,7 @@ Classifier: Programming Language :: Python :: 3.11
16
16
  Classifier: Programming Language :: Python :: 3.12
17
17
  Classifier: Programming Language :: Python :: 3.13
18
18
  Classifier: Topic :: Database
19
- Requires-Python: >=3.11
19
+ Requires-Python: <3.14,>=3.11
20
20
  Requires-Dist: certifi>=2024.2
21
21
  Requires-Dist: clickhouse-connect[arrow]>=0.8
22
22
  Requires-Dist: dactopus-ossie-clickhouse[mcp]~=0.13.0
@@ -56,16 +56,23 @@ The executor knows nothing of Dactopus.
56
56
 
57
57
  ## Install
58
58
 
59
- Python 3.11 or later and [uv](https://docs.astral.sh/uv/).
59
+ [uv](https://docs.astral.sh/uv/). The runner runs on Python 3.11 to 3.13;
60
+ `--python 3.13` makes uv use that version, and download it when the
61
+ machine has none.
60
62
 
61
63
  ```bash
62
- uv tool install dactopus
64
+ uv tool install --python 3.13 dactopus
63
65
  ```
64
66
 
65
67
  The `dactopus` command gets its own environment with dbt, the dbt
66
68
  ClickHouse adapter and the executor. The machine needs no ClickHouse
67
69
  binaries; the runner connects to the client's ClickHouse server over HTTP.
68
70
 
71
+ `uv tool upgrade dactopus` updates it. An installation of 0.1.0 or
72
+ 0.1.1, which came from GitHub, moves to PyPI with
73
+ `uv tool install --force --python 3.13 dactopus`: `uv tool upgrade`
74
+ keeps it on the GitHub tag.
75
+
69
76
  Then, in the folder of the installation:
70
77
 
71
78
  ```bash
@@ -270,7 +277,7 @@ runner and what each was verified on:
270
277
 
271
278
  ## Development
272
279
 
273
- Python 3.11 or later and [uv](https://docs.astral.sh/uv/).
280
+ Python 3.11 to 3.13 and [uv](https://docs.astral.sh/uv/).
274
281
 
275
282
  ```bash
276
283
  uv sync
@@ -26,16 +26,23 @@ The executor knows nothing of Dactopus.
26
26
 
27
27
  ## Install
28
28
 
29
- Python 3.11 or later and [uv](https://docs.astral.sh/uv/).
29
+ [uv](https://docs.astral.sh/uv/). The runner runs on Python 3.11 to 3.13;
30
+ `--python 3.13` makes uv use that version, and download it when the
31
+ machine has none.
30
32
 
31
33
  ```bash
32
- uv tool install dactopus
34
+ uv tool install --python 3.13 dactopus
33
35
  ```
34
36
 
35
37
  The `dactopus` command gets its own environment with dbt, the dbt
36
38
  ClickHouse adapter and the executor. The machine needs no ClickHouse
37
39
  binaries; the runner connects to the client's ClickHouse server over HTTP.
38
40
 
41
+ `uv tool upgrade dactopus` updates it. An installation of 0.1.0 or
42
+ 0.1.1, which came from GitHub, moves to PyPI with
43
+ `uv tool install --force --python 3.13 dactopus`: `uv tool upgrade`
44
+ keeps it on the GitHub tag.
45
+
39
46
  Then, in the folder of the installation:
40
47
 
41
48
  ```bash
@@ -240,7 +247,7 @@ runner and what each was verified on:
240
247
 
241
248
  ## Development
242
249
 
243
- Python 3.11 or later and [uv](https://docs.astral.sh/uv/).
250
+ Python 3.11 to 3.13 and [uv](https://docs.astral.sh/uv/).
244
251
 
245
252
  ```bash
246
253
  uv sync
@@ -56,6 +56,34 @@ without Python weighs more then than the adapter's maturity. SQLMesh was
56
56
  ruled out: it needs a state database of its own, and ClickHouse is not
57
57
  fit for that role.
58
58
 
59
+ ## Python 3.11 to 3.13 (1 November 2026)
60
+
61
+ dbt-core 1.11 does not start on Python 3.14: it caps mashumaro below
62
+ 3.15, and `dbt --version` fails in mashumaro 3.14 with
63
+ `UnserializableField`. dbt-core 1.12.6 starts on 3.14 with mashumaro
64
+ 3.17 (3.15 and 3.16 fail) and built the same tables as 1.11 from the
65
+ same input: 4.3 million GA4 events and 489 Shopify orders, every table
66
+ equal in rows and in a hash of all columns, the same report. It was
67
+ not taken: 1.12 and 1.13.0b1 require `dbt-core-experimental-parser`, a
68
+ Rust binary in alpha, published on PyPI as a source package whose build
69
+ downloads a wheel from GitHub. An install then needs github.com, not
70
+ only PyPI ([dbt#15670](https://github.com/dbt-labs/dbt/issues/15670)),
71
+ and a certificate store in the Python that builds it: python.org's 3.14
72
+ without Install Certificates failed with `CERTIFICATE_VERIFY_FAILED`
73
+ ([dbt#15809](https://github.com/dbt-labs/dbt/issues/15809)). The wheels
74
+ cover macOS, Linux with glibc 2.28 or later and Windows on x86_64, no
75
+ Alpine ([dbt#15607](https://github.com/dbt-labs/dbt/issues/15607)). An
76
+ install that works the first time outweighs 3.14, which uv replaces by
77
+ a Python it downloads. Revisit when the parser ships wheels on PyPI or
78
+ becomes optional.
79
+
80
+ `requires-python = ">=3.11,<3.14"` alone does not keep a uv tool off
81
+ 3.14: uv 0.8.17 and 0.13.6 ignore the upper bound and installed 0.2.1
82
+ on 3.14, both with `--python 3.14` and on a machine whose only Python
83
+ was 3.14; pip refuses it. So the README passes `--python 3.13`, which
84
+ uv downloads when the machine has none, and every command refuses 3.14
85
+ with the command that reinstalls. Verified on macOS arm64.
86
+
59
87
  ## The word runner (8 October 2026)
60
88
 
61
89
  *Agent* is taken by the AI that talks to the MCP server. *Runner* over
@@ -1,12 +1,13 @@
1
1
  [project]
2
2
  name = "dactopus"
3
- version = "0.2.0"
3
+ version = "0.2.1"
4
4
  description = "Runner of Dactopus: loads sources into ClickHouse, builds the canonical tables, runs checks, serves the models over MCP"
5
5
  readme = "README.md"
6
6
  license = "Apache-2.0"
7
7
  license-files = ["LICENSE"]
8
8
  authors = [{ name = "Alex Kosachev" }]
9
- requires-python = ">=3.11"
9
+ # dbt-core 1.11 does not start on 3.14 (docs/design.md, "Python 3.11 to 3.13").
10
+ requires-python = ">=3.11,<3.14"
10
11
  keywords = ["clickhouse", "ecommerce", "ga4", "shopify", "mcp"]
11
12
  classifiers = [
12
13
  "Development Status :: 2 - Pre-Alpha",
@@ -167,8 +167,22 @@ _FAILURES = (
167
167
  )
168
168
 
169
169
 
170
+ # The first Python dbt-core 1.11 does not start on. uv ignores the upper bound of
171
+ # requires-python, so a uv tool can land on it; docs/design.md, "Python 3.11 to 3.13".
172
+ UNSUPPORTED_PYTHON = (3, 14)
173
+
174
+
170
175
  def main(argv: list[str] | None = None) -> int:
171
176
  args = _parser().parse_args(argv)
177
+ if sys.version_info[:2] >= UNSUPPORTED_PYTHON:
178
+ version = ".".join(map(str, sys.version_info[:2]))
179
+ print(
180
+ f"dactopus {args.command}: dactopus runs on Python 3.11 to 3.13, not on {version}, "
181
+ "where dbt does not start. Reinstall it with: "
182
+ "uv tool install --force --python 3.13 dactopus",
183
+ file=sys.stderr,
184
+ )
185
+ return 1
172
186
  try:
173
187
  if args.command == "init":
174
188
  return _init(args)
@@ -1,3 +1,4 @@
1
+ import sys
1
2
  from pathlib import Path
2
3
 
3
4
  import pytest
@@ -19,6 +20,14 @@ def test_unknown_command_is_refused():
19
20
  assert exit_info.value.code == 2
20
21
 
21
22
 
23
+ def test_an_unsupported_python_is_refused_with_the_reinstall_command(tmp_path, monkeypatch, capsys):
24
+ monkeypatch.setattr(cli, "UNSUPPORTED_PYTHON", sys.version_info[:2])
25
+ path = tmp_path / "dactopus.yaml"
26
+ assert main(["init", "--config", str(path)]) == 1
27
+ assert not path.exists()
28
+ assert "uv tool install --force --python 3.13 dactopus" in capsys.readouterr().err
29
+
30
+
22
31
  def test_init_writes_the_sample(tmp_path, capsys):
23
32
  path = tmp_path / "dactopus.yaml"
24
33
  assert main(["init", "--config", str(path)]) == 0