astral-sh/uv

Allow `--isolated` with script execution

Open

#15919 opened on Sep 17, 2025

View on GitHub
 (2 comments) (0 reactions) (0 assignees)Rust (84,934 stars) (3,111 forks)batch import
enhancementgood first issue

Description

Right now, we ignore the flag and display a warning

❯ uv run --isolated --script example.py
warning: `--isolated` is a no-op for Python scripts with inline metadata, which always run in isolation

but now that we changed scripts to use a stable path, we should allow --isolated to opt-out of that, e.g., for people in situations like https://github.com/astral-sh/uv/issues/15918

Contributor guide

Tech stack
rustpython
Domain
clideveloper experience
Issue type
feature
DifficultyEstimated implementation difficulty for a new contributor, from 1 for very small changes to 5 for expert-level work.
3
Estimated timeA rough time range for an experienced contributor to investigate, implement, test, and prepare a pull request.
1-3 hours
Activity statusHow available the issue appears right now: fresh, active, stale, blocked, or waiting on maintainer input.
fresh
ClarityHow clearly the issue explains the expected change, acceptance criteria, and next step.
clear
Prerequisites
Basic RustFamiliarity with uv script execution
Newbie friendlinessA 1-100 score estimating how approachable this issue is for first-time contributors.
75
Research direction
The issue asks to allow the ` isolated` flag with script execution instead of ignoring it. Currently, `uv run isolated script example.py` shows a warning that the flag is a no op. The change should remove the warning and make ` isolated` opt out of the stable path behavior for scripts. Look at how scripts use the stable path (refer to issue #15918) and modify the relevant code in the CLI argument handling. Check the comments on this issue for any additional context or maintainer input.