chore: bump pixi.lock to maturin 1.13.1 to fix py314t build#889
Merged
Conversation
The `maturin>=1.9` constraint from #888 resolved to 1.10.2 in the previous lockfile, which still raises "Unsupported Python interpreter for cross-compilation" for free-threaded CPython 3.14t venvs. The offending code path was removed in the v1.13 resolver refactor (PyO3/maturin commit 98c4d728). Bumping the lock to 1.13.1 lets `pixi run -e py314t py-build` succeed. Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>
|
edgarriba
approved these changes
Apr 22, 2026
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
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.
Summary
pixi.lockso thematurin>=1.9constraint from fix: pin maturin>=1.9 to support Python 3.14t free-threaded builds #888 resolves to 1.13.1 across every pixi env (previously stuck at 1.10.2).py3.14t-linuxCI job, which still failed on fix: pin maturin>=1.9 to support Python 3.14t free-threaded builds #888-inclusive main with the same original error:Why 1.13.1 specifically
I grepped
PyO3/maturinfor the error string across release tags:The offending branch was deleted in PyO3/maturin@98c4d728 (PR #3032, "refactor: unified interpreter resolution pipeline"). The new
InterpreterResolverhandles free-threaded CPython via anabiflags == \"t\"check and accepts a real venv executable path asCandidate::Executable, instead of falling into the pre-refactor cross-compile bail. conda-forge ships v1.13.1 today, so a plainpixi update maturinpicks it up.Context
maturin = \"*\"→\">=1.9\"inpixi.toml/kornia-py/pyproject.tomlbut did not regeneratepixi.lock. Pixi pins to the lock, so the manifest bump was effectively inert for already-locked environments.pixi.lockchanges here; no manifest edits.Test plan
pixi run -e py314t py-buildsucceeds (formerly failed in 50s atmaturin develop).pixi run -e py314t py-test-threadedpasses.py3.X-linuxjobs still pass with the newer maturin (1.13.1 is backwards-compatible with 3.8–3.14).🤖 Generated with Claude Code