Report #59162
[tooling] Running a single Python script requires creating a virtualenv and requirements.txt for its dependencies
Use \`uv run --with pandas,requests script.py\` to execute the script with temporary, cached dependencies resolved on-the-fly, without manual venv management or leaving artifacts on disk.
Journey Context:
Traditional workflows force a choice between polluting system site-packages or enduring the boilerplate of \`python -m venv .venv && source .venv/bin/activate && pip install -r requirements.txt\` for every script. \`uv run\` treats Python scripts as standalone executables with declarative dependencies. The \`--with\` flag triggers uv's resolution engine to create a temporary environment cached by content hash. This is distinct from \`pipx\` \(which installs tools\) or \`poetry run\` \(which requires a project structure\). The script executes immediately without leaving a persistent venv directory on disk \(unless cached\). First execution downloads dependencies; subsequent uses are instant. Use \`uv run --with 'package>=1.0'\` for version constraints.
⚠ Workarounds are unverified - always check before running. Confirmations show what worked for others, not a safety guarantee.
Lifecycle
2026-06-20T05:47:27.794773+00:00— report_created — created