Python 3.10-3.13 are only listed in the Install via uv section

[loganjohnson0]

I was just confused about this when I was looking at my other idea: #17166. When I do the following:
New Folder from Template -> Python Project -> (just choose defaults on "Folder Name and Location") -> Python Environment

uv only shows Python 3.10 to 3.13 as options to install. In reading the release notes, Python 3.15 (and thus 3.14) are supported now. Should they be options to select to install? I do have some various Pythons already installed, so maybe uv in this case only lets me install ones similar to what I already have? Shouldn't it let me install newer/supported versions beyond what I have installed?

Caveat: I don't use Python much, but I was just playing around as I was checking on my other comment in #17166 so maybe this is just a me issue!

Positron Version: 2026.11.0 (user setup) build 308
Code - OSS Version: 1.138.0
Commit: e57aeda
Date: 2026-11-05T00:50:26+00:00
Electron: 42.11.18
Chromium: 148.0.7778.280
Node.js: 24.19.0
V8: 14.8.178.38-electron.0
OS: Windows_NT x64 10.0.26200

[Pavel-Shcherbo]

The list is not limited to versions similar to the Pythons you already have installed. In the commit you quoted, the picker asks uv for its managed-Python list, including entries marked <download available>.

The relevant code is:

• getAvailablePythonVersions: runs uv --color never python list --managed-python on Windows x64, filters pre-releases, and allows Python versions from 3.10 up to (but excluding) 3.16.
• getUvPythonVersions: uses that result when it is nonempty. Its fallback list already contains 3.15 and 3.14, but it does not merge those into a nonempty uv result.

So an older uv installation/catalog is one possibility: if it returns stable versions only through 3.13, that shorter list wins. That is a hypothesis for your machine, rather than a confirmed diagnosis.

Could you check these in a Positron PowerShell terminal?

Get-Command uv -All | Select-Object Source
uv --version
uv --color never python list --managed-python

If uv's output also stops at 3.13, update uv using its original installation method, then fully restart Positron and try the picker again. uv's upgrade instructions distinguish standalone installations (uv self update) from package-manager installations. If that output already contains stable 3.14/3.15 while the picker omits them, the next thing to check is whether the extension host is finding a different uv executable; its Python logs would help distinguish that case.

I checked the source at your exact commit and ran seven isolated checks of its version-list functions with controlled uv output, including downloadable 3.14/3.15, an older nonempty list, pre-release filtering and fallback behavior. I have not reproduced the Windows IDE session or run your installed uv.

[loganjohnson0]

Yes that now makes sense......I had originally thought that Positron would use the newest version, but it defaults to installed versions if you have it per the docs

Use existing uv: If you have uv already installed system-wide, Positron uses your existing installation.

I had:

uv 0.8.10 (7e817bafd 2025-08-13)

and upgrading to:

uv 0.13.7 (316c827e0 2026-11-03 x86_64-pc-windows-msvc)

solves my question!

Sorry for the noise and silly question!

[austin3dickey]

Thanks for the answer @Pavel-Shcherbo, and thanks for the question @loganjohnson0! It wasn't silly; I think this is confusing too. I created #17205 to hopefully make this situation better.