Skip to content
Merged
Show file tree
Hide file tree
Changes from all commits
Commits
File filter

Filter by extension

Filter by extension


Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
9 changes: 5 additions & 4 deletions poetry.lock

Some generated files are not rendered by default. Learn more about how customized files appear on GitHub.

2 changes: 1 addition & 1 deletion pyproject.toml
Original file line number Diff line number Diff line change
Expand Up @@ -11,7 +11,7 @@ license = "MIT"
[tool.poetry.dependencies]
python = ">=3.11,<3.15"
views-pipeline-core = ">=2.1.3,<3.0.0"
views-frames = ">=1.0,<2"
views-frames = ">=1.10.2,<2"
pyarrow = ">=16.1.0,<17.0.0"

[build-system]
Expand Down
14 changes: 11 additions & 3 deletions tests/fixtures/wire_contract/README.md
Original file line number Diff line number Diff line change
Expand Up @@ -29,6 +29,14 @@ injected fixed literals (`run_id="fixture_run_0"`, `generated_at="2026-07-15T00:
## Regeneration

`PYTHONPATH=. python3 scripts/build_wire_fixture.py` — byte-reproducible **with the pinned
tool versions** (numpy per lockfile, `pyarrow 16.1.0`, `views_frames 1.0.0`; parquet bytes
vary across pyarrow versions). The committed bytes + `SHA256SUMS` are canonical regardless.
**A change to this fixture is a change to the contract (§10)** — do not regenerate casually.
tool versions** (numpy per lockfile, `pyarrow 16.1.0`). The committed bytes + `SHA256SUMS`
are canonical regardless. **A change to this fixture is a change to the contract (§10)** —
do not regenerate casually.

**`pyarrow` is the version-sensitive one; `views_frames` is not.** Parquet bytes vary
across pyarrow versions — that is why the pin is `>=16.1.0,<17.0.0` and why a local
pyarrow 23.x fails byte-parity while CI passes (register **C-72**). `views_frames` sits
above it: the fixture was generated under `1.0.0`, CI has reproduced it continuously under
`1.6.0`, and `1.10.2` was verified to regenerate **all five artifacts byte-identically**
before the pin was raised (2026-08-02). Raising it again does not require regenerating the
fixture — but it does require proving that, the same way.
Loading