feat: install script environments without running - #6923
Merged
Conversation
manzt
force-pushed
the
manzt/install-script
branch
5 times, most recently
from
August 31, 2026 16:45
a23ead9 to
4d76f9d
Compare
baszalmstra
requested changes
Sep 1, 2026
`pixi update --script` refreshes the resolution for a script, but it does not materialize the environment. Until now, the only way to prepare that environment was `pixi run --script`, which also executes the script. These changes add `pixi install --script` to materialize the same cached environment without running user code. Reuse the shared install path so script caches and adjacent lock files follow the same install semantics as workspaces.
manzt
force-pushed
the
manzt/install-script
branch
5 times, most recently
from
September 1, 2026 15:22
abb29b9 to
38040e5
Compare
manzt
force-pushed
the
manzt/install-script
branch
from
September 1, 2026 20:01
38040e5 to
14971e6
Compare
baszalmstra
approved these changes
Sep 2, 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
2 participants
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.
I originally thought
pixi update --script(#6893) was enough for tools that manage PEP 723 script environments. However, it only refreshes the resolution, but it does not materialize the environment. Today, the only command that does both ispixi run --script, which also executes the script.These changes add
pixi install --script <PATH>to materialize the same environment thatpixi run --scriptwould use, without running user code. It reuses the existing script resolution cache or adjacent lock file and the shared install path and does not introduce another script environment model.The lifecycle is now explicit where:
pixi update --scriptselects newer compatible versions (metadata only)pixi install --scriptreconciles and materializes the environment without broadly upgradingpixi run --scriptsame as above, but then runs user code after installing.For example, this makes it possible to replace uv in marimo's
--sandboxflow and use Pixi to install and manage packages without requiring uv. Working branch in marimo: