docs(register): C-104 — the lock installs on cp311 only - #296
Merged
Conversation
Running `poetry install` took the suite from 26 failed/470 passed to 6 failed/490 passed (pipeline-core 2.3.0 -> 3.0.1), then died building levenshtein 0.20.9 from source. What remains is one drifted package, pyarrow 23.0.1 against 16.1.0 locked, and all six failures are that cause: five C-72 byte-parity checks plus the lock check reporting it. Wheel availability, measured against the index: pyarrow 16.1.0 and levenshtein 0.20.9 both ship cp311; levenshtein stops at cp311, pyarrow at cp312. levenshtein is capped >=0.20,<0.21 by ingester3, so the ceiling is upstream. poetry.lock installs on cp311 alone. CI runs 3.11 and the delivery's conda prefix is 3.11.15 with pyarrow 16.1.0 — both match the lock. Only the developer venv (3.13.7) is off, and the command everyone is told to run cannot bring it back. That makes the entry's own mitigation half wrong in the way it names as a failure: test_locked_environment rules out printing a remedy that cannot work, and on 3.12+ its "Run `poetry install`" line does exactly that. Trigger and Location updated; what closes the entry is now a rebuild on 3.11, not a reinstall. The second half — pyproject declaring >=3.11,<3.15 when only 3.11 resolves — is filed as #295, being a declaration defect rather than an environment one. Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com>
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Folds the 2026-08-22 measurements into C-104 and updates its Trigger, Location and closing condition.
The finding:
poetry installcannot succeed on the developer venv's Python 3.13. It got as far as pipeline-core 2.3.0 → 3.0.1 (26 failed → 6 failed, 470 → 490 passed) and then failed buildinglevenshtein 0.20.9, whichingester3caps>=0.20,<0.21and which publishes no 3.12+ wheel.pyarrow 16.1.0has no cp313 wheel either. The lock resolves on cp311 alone.CI (3.11) and the delivery's conda prefix (3.11.15, pyarrow 16.1.0) both match the lock exactly — no production or CI impact. Only the developer venv is off, and the remedy
test_locked_environmentprints is advice that cannot work there, which is precisely the failure mode that test's own design notes rule out.The
pyprojecthalf —python = ">=3.11,<3.15"declaring three interpreters when one resolves — is #295.Prose only; no code, no entry added, header counts unchanged.
🤖 Generated with Claude Code