Use uv when setting up a new project python environment in Positron

[fcamineiro]

I'm testing the Positron project manager to set up a new Python project using uv, but it's returning that uv is not installed (check screenshot). I have uv installed at the terminal (omz) level, but I don't know why Positron is not detecting it. How does one handle that?

[austin3dickey]

Hey @fcamineiro, thanks for the question. Some thoughts that may help solve the issue:

• Does a restart of Positron help?
• In a new (non-Positron) terminal, if you do which uv (or where uv for Windows), what does it print?
• How exactly did you install uv? Was it one of the ways in the docs or e.g. an oh-my-zsh plugin or something?

If these questions don't help, let me get some more info. Could you please attach:

• the output of the About Positron menu item
• some logs:
  • Go to the Python Language Pack channel in the Output Panel
  • Click the "clear output" button next to the channel selector
  • Click the "set log level" gear button next to that, and choose Trace, and then Set As Default in the same menu
  • Restart Positron
  • Go back to the Python Language Pack channel, and in the ... menu select Save Output As...
  • Upload that file here

[fcamineiro]

Thanks, @austin3dickey! I updated uv using the standalone installer, and Positron was able to see it.

[austin3dickey]

Ah, great! We'll definitely want to make sure that other uv installation methods work too.

My best guess is that the PATH wasn't being modified correctly upon opening Positron. For example, if I have uv at ~/.cargo/bin/uv, Positron does find it because in my ~/.profile there exists the line . "$HOME/.cargo/env, which adds ~/.cargo/bin to my PATH. But if something weren't quite right there, I could see a scenario where uv isn't on the PATH upon opening Positron, so it's not found.

Sounds like the standalone installer fixed whatever PATH modification was necessary. 🤷

[fcamineiro]

Indeed, that seems to be the case!