Add support for `--upgrade` in `uv python install` by zanieb · Pull Request #16676 · astral-sh/uv

zanieb · 2025-11-10T23:37:31Z

This allows us to suggest uv python install --upgrade 3.14 as the canonical way to get the latest patch version of a given Python regardless of whether it is installed already. Currently, you can do uv python upgrade 3.14 and it will install it, but I'd like to remove that behavior as I find it very surprising.

codspeed-hq · 2025-11-11T17:31:41Z

CodSpeed Performance Report

Merging #16676 will not alter performance

_{Comparing zb/install-upgrade (7b05e36) with main (e28dc62)}

Summary

✅ 6 untouched

konstin · 2025-11-13T11:13:43Z

crates/uv/tests/it/python_install.rs

+        .with_managed_python_dirs();
+
+    // Provide `--upgrade` as an `install` option without any versions
+    uv_snapshot!(context.filters(), context.python_install().arg("--upgrade"), @r"


Upgrade without an explicit version has a quirk: When pinning a patch version in .python_versions, it errors. I expect that some users will do uv python install --upgrade by default because they want to have the latest patch version, and will get confused by this too, especially when they don't realize that there's a .python_versions.

$ uv python install --upgrade error: `uv python install --upgrade` only accepts minor versions, got: 3.14.0

There's a workflow that's between uv python install and uv python upgrade: I want to install Python at the version that the project requires, upgraded to the latest patch version if not already at that, unless the project pins a patch version. Trying to emulate that with uv python install --upgrade can lead to the error above.

Ah thanks. I'll look into that.

I think it might just need to be a hint when the request comes from a .python-version file?

A hint would do it.

I think we can do even better, but I'll plan to do that in a follow-up.

konstin · 2025-11-13T11:25:27Z

crates/uv/src/commands/python/install.rs

+                    "There are no installed versions to upgrade"
+                )?;
+            }
+            PythonUpgrade::Enabled(PythonUpgradeSource::Install) => {


Review note: This is reachable by creating an empty .python_versions file (unlike the branch above, which by default looks at installed Pythons)

konstin · 2025-11-13T11:40:54Z

crates/uv/tests/it/python_install.rs

+    ----- stderr -----
+    Installed Python 3.14.0 in [TIME]
+     + cpython-3.14.0-[PLATFORM] (python3.14)
+    ");


Another quirk: The output log for plain without any pin is the same with and without upgrade. I'd have expected something like "latest patch version Python 3.14.0 is already installed".

$ uv python install Python is already installed. Use `uv python install <request>` to install another version. $ uv python install --upgrade Python is already installed. Use `uv python install <request>` to install another version.

Similar to what an explicit request tells you:

$ uv python install --upgrade 3.14 Python 3.14 is already on the latest supported patch release

It's pre-existing, but it would also be nice if uv python install and uv python install --upgrade 3.14 would tell me the version that is installed that they consider latest.

I think I might expect this to error asking for a request? but you're right the message should change if we don't.

Banning uv python install --upgrade without a python input from anywhere sounds good to me.

This MR contains the following updates: | Package | Update | Change | |---|---|---| | [astral-sh/uv](https://github.com/astral-sh/uv) | patch | `0.9.9` -> `0.9.10` | MR created with the help of [el-capitano/tools/renovate-bot](https://gitlab.com/el-capitano/tools/renovate-bot). **Proposed changes to behavior should be submitted there as MRs.** --- ### Release Notes <details> <summary>astral-sh/uv (astral-sh/uv)</summary> ### [`v0.9.10`](https://github.com/astral-sh/uv/blob/HEAD/CHANGELOG.md#0910) [Compare Source](astral-sh/uv@0.9.9...0.9.10) Released on 2025-11-17. ##### Enhancements - Add support for `SSL_CERT_DIR` ([#16473](astral-sh/uv#16473)) - Enforce UTF‑8-encoded license files during `uv build` ([#16699](astral-sh/uv#16699)) - Error when a `project.license-files` glob matches nothing ([#16697](astral-sh/uv#16697)) - `pip install --target` (and `sync`) install Python if necessary ([#16694](astral-sh/uv#16694)) - Account for `python_downloads_json_url` in pre-release Python version warnings ([#16737](astral-sh/uv#16737)) - Support HTTP/HTTPS URLs in `uv python --python-downloads-json-url` ([#16542](astral-sh/uv#16542)) ##### Preview features - Add support for `--upgrade` in `uv python install` ([#16676](astral-sh/uv#16676)) - Fix handling of `python install --default` for pre-release Python versions ([#16706](astral-sh/uv#16706)) - Add `uv workspace list` to list workspace members ([#16691](astral-sh/uv#16691)) ##### Bug fixes - Don't check file URLs for ambiguously parsed credentials ([#16759](astral-sh/uv#16759)) ##### Documentation - Add a "storage" reference document ([#15954](astral-sh/uv#15954)) </details> --- ### Configuration 📅 **Schedule**: Branch creation - At any time (no schedule defined), Automerge - At any time (no schedule defined). 🚦 **Automerge**: Disabled by config. Please merge this manually once you are satisfied. ♻ **Rebasing**: Whenever MR becomes conflicted, or you tick the rebase/retry checkbox. 🔕 **Ignore**: Close this MR and you won't be reminded about this update again. --- - [ ] If you want to rebase/retry this MR, check this box --- This MR has been generated by [Renovate Bot](https://github.com/renovatebot/renovate).

zanieb added the cli Related to the command line interface label Nov 10, 2025

zanieb had a problem deploying to uv-test-registries November 10, 2025 23:39 — with GitHub Actions Error

zanieb force-pushed the zb/install-upgrade branch from 46ab81a to 8231be2 Compare November 10, 2025 23:40

zanieb temporarily deployed to uv-test-registries November 10, 2025 23:42 — with GitHub Actions Inactive

zanieb force-pushed the zb/install-upgrade branch from 8231be2 to 1adb859 Compare November 11, 2025 00:20

zanieb temporarily deployed to uv-test-registries November 11, 2025 00:22 — with GitHub Actions Inactive

zanieb force-pushed the zb/install-upgrade branch from 1adb859 to 8196e5c Compare November 11, 2025 17:15

zanieb temporarily deployed to uv-test-registries November 11, 2025 17:17 — with GitHub Actions Inactive

zanieb marked this pull request as ready for review November 11, 2025 17:19

zanieb added the preview Experimental behavior label Nov 11, 2025

zanieb requested a review from konstin November 12, 2025 13:55

konstin approved these changes Nov 13, 2025

View reviewed changes

zanieb added 2 commits November 13, 2025 08:23

Add support for --upgrade in uv python install

2fc75a5

Review

7b05e36

zanieb force-pushed the zb/install-upgrade branch from 8196e5c to 7b05e36 Compare November 13, 2025 14:32

zanieb temporarily deployed to uv-test-registries November 13, 2025 14:36 — with GitHub Actions Inactive

zanieb merged commit f5ce5b4 into main Nov 13, 2025
100 checks passed

zanieb deleted the zb/install-upgrade branch November 13, 2025 15:55

BrewTestBot mentioned this pull request Nov 17, 2025

uv 0.9.10 Homebrew/homebrew-core#254745

Merged

Provide feedback

Saved searches

Use saved searches to filter your results more quickly

Comments

Add support for `--upgrade` in `uv python install`#16676

Add support for `--upgrade` in `uv python install`#16676
zanieb merged 2 commits intomainfrom
zb/install-upgrade

zanieb commented Nov 10, 2025 •

edited

Loading

Uh oh!

codspeed-hq bot commented Nov 11, 2025 •

edited

Loading

Uh oh!

konstin Nov 13, 2025

Uh oh!

zanieb Nov 13, 2025

Uh oh!

zanieb Nov 13, 2025

Uh oh!

konstin Nov 13, 2025

Uh oh!

zanieb Nov 13, 2025

Uh oh!

konstin Nov 13, 2025

Uh oh!

konstin Nov 13, 2025

Uh oh!

zanieb Nov 13, 2025

Uh oh!

konstin Nov 13, 2025

Uh oh!

Uh oh!

Reviewers

Assignees

Labels

Projects

Milestone

Development

Uh oh!

2 participants

Comments

Conversation

zanieb commented Nov 10, 2025 • edited Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

Uh oh!

codspeed-hq bot commented Nov 11, 2025 • edited Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

Merging #16676 will not alter performance

Summary

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Uh oh!

Reviewers

Assignees

Labels

Projects

Milestone

Development

Uh oh!

2 participants

zanieb commented Nov 10, 2025 •

edited

Loading

codspeed-hq bot commented Nov 11, 2025 •

edited

Loading