Repository navigation
Conversation
Picking uv to create an environment without uv installed failed with "Error while creating virtual environment". The uv provider now asks to install uv first, and the requirements.txt / pyproject.toml prompt offers uv (installing it on Yes) whenever python.allowUvPythonInstall is on. Fixes #16192
ensureUvInstalled now refuses to install uv when python.allowUvPythonInstall is off, covering the Create Environment wizard, the New Folder flow's Install uv button, the global environment command and installPythonViaUv. The setting description now says it covers installing uv, not just the interpreter picker.
|
E2E Tests 🚀 Why these tags?
More on automatic tags from changed files. |
|
/explore |
|
🔎 Exploratory testing f0e1067 1 moderate · 2 minor |
I fixed this... when uv is not installed and
If uv is already installed, it's still listed (first, as before). The setting only stops Positron from installing uv, not from using an existing one. |
uv is no longer offered when it is missing and python.allowUvPythonInstall is off, so the step never reaches the disabled state.
|
@midleman @isabelizimm Why are we showing the "Python: Install Python via uv" command in the command palette when the |
| "python.environmentProviders.enabled.markdownDescription": "Configures which Python environment providers are enabled in Positron. Check the box to enable or uncheck the box to disable an environment provider.\n\nRequires a restart to take effect.", | ||
| "python.environmentProviders.enable.markdownDeprecationMessage": "Deprecated. Use `#python.environmentProviders.enabled#` instead.", | ||
| "python.allowUvPythonInstall.markdownDescription": "Allow installing Python via uv from the interpreter picker. When enabled, shows an option to install Python using [uv](https://docs.astral.sh/uv/) if no suitable Python interpreter is found.", | ||
| "python.allowUvPythonInstall.markdownDescription": "Allow Positron to install [uv](https://docs.astral.sh/uv/) and to install Python with uv. When disabled, Positron does not offer to install uv anywhere, and the interpreter picker does not offer to install Python with uv.", |
There was a problem hiding this comment.
and the interpreter picker does not offer to install Python with uv.
Is the video in the PR description out of date? It shows the opposite of what the setting description says
That's a valid question. I assume it's hideable under that circumstance? If we confirm that's what we want, I can make that update. 👍 |
|
@dhruvisompura, i made a few updates:
|
…r doc (#16574) ### Summary One command now runs a whole exploratory test, locally and in CI, and the verifier flags findings that match issues closed as not planned. - `pipeline.mjs run` runs explore, verify, isolate and edit in order; locally each agent is a `claude -p` session. - CI now isolates UNRESOLVED findings, and both sides retry a failed verifier once. - Local runs show cost on the Run tile, stream a live feed to the shell, and take a time limit you can change mid-run. - The verifier shows an advisory "Intended?" column for findings matching not-planned issues. - New `CONTRIBUTING.md` maps what to edit for each kind of change; bumped to 1.57. ### Release Notes #### New Features - N/A #### Bug Fixes - N/A ### Validation Steps CI run on #16511 passed ([run](https://github.com/posit-dev/positron/actions/runs/37990923444)); the CI isolator path is still untested against a real agent.
Fixes #16192
Creating a venv with uv no longer fails when uv isn't installed. Positron offers to install uv first, unless
python.allowUvPythonInstallis off.Demo - uv install off/disabled
uv-install-off.mp4
Demo - uv install on/enabled
uv-install-on.mp4
Updated setting veribage
Release Notes
New Features
Bug Fixes
Validation Steps
@:interpreter @:new-folder-flow
python.allowUvPythonInstallto false (uv still missing): uv isn't listed in Create Environment or the New Folder flow's Environment Creation dropdown.python.allowUvPythonInstallstill false, Python: Install Python via uv isn't in the Command Palette.