Summary

uvx is silently discarding the most recent versions of tools if they are not compatible with the "default Python version" it initially selects, even when it has access to a Python version that is compatible.

For example, in my system, python is linked to python 3.12, but python 3.14 is available.

$ uvx dedlin --version
1.19.4
$ uvx dedlin@latest --version
1.20.0
$ uvx dedlin --version
1.19.4

This appears to contradict the documentation at https://docs.astral.sh/uv/concepts/tools/#tool-versions which states that "uvx will use the latest available version of the requested tool on the first invocation" -- this appears to currently only be true if you run with @latest. Could the default behaviour be changed to match the behaviour of @latest on first invocation? (IMO it should outright fail if it can't run the latest version due to not having a compatible Python version, rather than silently downgrading -- though maybe not if --python=... is explicitly passed?)

Platform

RHEL 8 x86_64

Version

uv 0.11.17 (x86_64-unknown-linux-gnu)

Python version

Python 3.12.13