Activate venv from script metadata?

[ianhi]

I'd like to be able to access the venv of a script for LSP integration outside the context of a project. i.e. a one-off script with dependencies decalred per pep 723 (https://docs.astral.sh/uv/guides/scripts/#declaring-script-dependencies). Is this possible to support?

I'm hoping the answer is yes because I think when I when I uv run a script it creates a cache somewhere of the packages so they much be available somewhere

Maybe this is some sort of lead: https://stackoverflow.com/a/79544311/835607

[benomahony]

I've not tried this but looking at the docs I think it should work? Or have you tried this and it definitely doesn't work?

[alsa64]

I make heavy use of this as well, for all kinds of utility scripts, here is an example:

#!/usr/bin/env -S uv run --script
# /// script
# requires-python = ">=3.12"
# dependencies = [
#  "requests",
#  "tqdm",
#  "python-dotenv",
# ]
# ///

That will create a temporary venv with all the declared dependencies.

We can get the path to the venv using bash and uv:

uv run - <<EOF
import sys, os
print(os.path.dirname(os.path.dirname(sys.executable)))
EOF

Three examples:

❯ uv run - <<EOF
import sys, os
print(os.path.dirname(os.path.dirname(sys.executable)))
EOF
/Users/vyls/.local/share/uv/python/cpython-3.13.4-macos-aarch64-none

~/Projects/ComfyUI
❯ uv run --with pandas - <<EOF
import sys, os
print(os.path.dirname(os.path.dirname(sys.executable)))
EOF
Installed 6 packages in 68ms
/Users/vyls/.cache/uv/archive-v0/dfF1HenudkJzEb6QXd-j9

~/Projects/ComfyUI
❯ uv run - <<EOF
#!/usr/bin/env -S uv run --script
# /// script
# requires-python = ">=3.12"
# dependencies = [
#  "pandas",
# ]
# ///
import sys, os
print(os.path.dirname(os.path.dirname(sys.executable)))
EOF
Installed 6 packages in 31ms
/Users/vyls/.cache/uv/environments-v2/c97b16c2e75d107c

This could likely be adapted to lua as well.