undefined | Better HN

0 pointsAlphaSite1y ago0 comments

Usually the VENV and import lines are enough

0 comments

How do you determine where the venv is? AFAIK, uv run in script mode creates the venv in some random temporary directory.

I don’t know of a convenient way of doing it, but a clumsy way of doing it is to run this in your script:

  import os
  
  print(os.environ['VIRTUAL_ENV'] + '/bin/python')

Then, e.g. in VS Code, you bring up the command palette, run Python: Select Interpreter, and enter the result.

uv v0.6.10 has just been released with a more convenient way of doing this:

    uv python find --script foo.py

j / k navigate · click thread line to collapse

How do you determine where the venv is? AFAIK, uv run in script mode creates the venv in some random temporary directory.

I don’t know of a convenient way of doing it, but a clumsy way of doing it is to run this in your script:

  import os
  
  print(os.environ['VIRTUAL_ENV'] + '/bin/python')

Then, e.g. in VS Code, you bring up the command palette, run Python: Select Interpreter, and enter the result.

uv v0.6.10 has just been released with a more convenient way of doing this:

    uv python find --script foo.py

j / k navigate · click thread line to collapse