Require the command in `uvx <name>` to be available in the Python environment #11603

zanieb · 2025-02-18T19:29:25Z

Includes a few small minor changes to the messaging, but the primary change is that in, e.g., uvx foo, if the foo package does not provide the foo executable we will no longer execute an arbitrary foo executable if present on the PATH. This prevents confusing and surprising behavior, such as the user reported where they did uv tool install foobar (which provides foo) then uvx foo (which does not provide foo) later falls back to the executable provided by foobar since it's on the PATH. We don't enforce this for --from, so things like uvx --from foo bash -c "..." are still totally valid. We also still allow uvx foo where the foo executable is provided by a dependency of foo instead of foo itself.

Most of the diff here is consolidating the logic of the hint_on_not_found and warn_executable_not_provided_by_package utilities.

zanieb · 2025-02-18T20:04:49Z

crates/uv/tests/it/tool_run.rs

-    The following executables are provided by `black`:
-    - black
-    - blackd
-    Consider using `uv tool run --from black <EXECUTABLE_NAME>` instead.


The user is already using --from here, I don't think we should hint it again.

It's intended to be shown for like

❯ uvx fastapi-cli Installed 21 packages in 46ms The executable `fastapi-cli` was not found. warning: An executable named `fastapi-cli` is not provided by package `fastapi-cli`. The following executables are provided by `fastapi-cli`: - fastapi Consider using `uvx --from fastapi-cli <EXECUTABLE_NAME>` instead.

zanieb · 2025-02-18T20:05:35Z

crates/uv/tests/it/tool_run.rs

    success: false
    exit_code: 1
    ----- stdout -----
-    The executable `fastapi-cli` was not found.


We no longer attempt to execute this / succeed if it's on the PATH. Instead, we exit early.

Arguably, this is breaking — but I think this is a bug.

Yeah, I think as a user I wouldn't expect uvx to execute something just because it's on the PATH

zanieb · 2025-02-18T20:06:47Z

crates/uv/tests/it/tool_run.rs

+    The following executables are available:
+    - change_wheel_version
+
+    Use `uv tool run --from change-wheel-version change_wheel_version` instead.


I'm sort of tempted to just run the command when it matches the module-normalized package name :)

It does seem designed to confound the user. But are there cases where this could be a coincidence?

I can't really think of one, no.

Tracking in #12976

crates/uv/src/commands/tool/run.rs

crates/uv/tests/it/tool_run.rs

crates/uv/src/commands/tool/run.rs

jtfmumm · 2025-04-18T15:18:20Z

crates/uv/src/commands/tool/run.rs

+}
+
+impl std::fmt::Display for ExecutableProviderPackages<'_> {
+    fn fmt(&self, f: &mut std::fmt::Formatter<'_>) -> std::fmt::Result {


It seems surprising that Display doesn't display the representation of the type but warning and error information. Should this be a separate dedicated function or method?

I'm not sure, the type only exists for the purpose of rendering these messages. Previously, it was a function that called warn_user and println directly but here I want the caller to be able to make that decision and I think Display is the easiest way to do that. I think I'd just end up needing into introduce a separate type, like ExecutableProviderPackagesDisplay that implements Display? Or I'd need to implement like fn message(&self)-> String and construct a string instead of using Formatter?

I was confused when I encountered writeln!(printer.stderr(), "{providers}")?; above (before seeing this code). I didn't understand why you would just log the providers without context. It seems pretty non-standard to have Display perform conditional logic and log warnings.

I'd recommend something like providers.log_warnings() (or something more descriptive) to accomplish what you're doing here. You could pass in printer.

perform conditional logic and log warnings.

To be clear, it only logs one warning (which we could omit, but I don't think it really hurts — it's a case that should never happen). The rest of it is just writing to the formatter.

I can't use a function that takes a printer because I want to be able to use it in warn_user_once.

I see this as the same thing as implementing Display on an error type, which we frequently include more context on. Would it be clearer if it was named like ExecutableProviderHints instead?

Yeah that would be clearer

That makes sense, thanks!

jtfmumm · 2025-04-18T15:25:19Z

Left a few comments but generally looks good.

…ironment (#11603) Closes #7804 Includes a few small minor changes to the messaging, but the primary change is that in, e.g., `uvx foo`, if the `foo` package does not provide the `foo` executable we will no longer execute an arbitrary `foo` executable if present on the `PATH`. This prevents confusing and surprising behavior, such as the user reported where they did `uv tool install foobar` (which provides `foo`) then `uvx foo` (which does not provide `foo`) later falls back to the executable provided by `foobar` since it's on the `PATH`. We don't enforce this for `--from`, so things like `uvx --from foo bash -c "..."` are still totally valid. We also still allow `uvx foo` where the `foo` executable is provided by a _dependency_ of `foo` instead of `foo` itself. Most of the diff here is consolidating the logic of the `hint_on_not_found` and `warn_executable_not_provided_by_package ` utilities.

This MR contains the following updates: | Package | Update | Change | |---|---|---| | [astral-sh/uv](https://github.com/astral-sh/uv) | minor | `0.6.16` -> `0.7.3` | 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.7.3`](https://github.com/astral-sh/uv/blob/HEAD/CHANGELOG.md#073) [Compare Source](astral-sh/uv@0.7.2...0.7.3) ##### Enhancements - Add `--dry-run` support to `uv self update` ([#9829](astral-sh/uv#9829)) - Add `--show-with` to `uv tool list` to list packages included by `--with` ([#13264](astral-sh/uv#13264)) - De-duplicate fetched index URLs ([#13205](astral-sh/uv#13205)) - Support more zip compression formats: bzip2, lzma, xz, zstd ([#13285](astral-sh/uv#13285)) - Add support for downloading GraalPy ([#13172](astral-sh/uv#13172)) - Improve error message when a virtual environment Python symlink is broken ([#12168](astral-sh/uv#12168)) - Use `fs_err` for paths in symlinking errors ([#13303](astral-sh/uv#13303)) - Minify and embed managed Python JSON at compile time ([#12967](astral-sh/uv#12967)) ##### Preview features - Build backend: Make preview default and add configuration docs ([#12804](astral-sh/uv#12804)) - Build backend: Allow escaping in globs ([#13313](astral-sh/uv#13313)) - Build backend: Make builds reproducible across operating systems ([#13171](astral-sh/uv#13171)) ##### Configuration - Add `python-downloads-json-url` option for `uv.toml` to configure custom Python installations via JSON URL ([#12974](astral-sh/uv#12974)) ##### Bug fixes - Check nested IO errors for retries ([#13260](astral-sh/uv#13260)) - Accept `musllinux_1_0` as a valid platform tag ([#13289](astral-sh/uv#13289)) - Fix discovery of pre-release managed Python versions in range requests ([#13330](astral-sh/uv#13330)) - Respect locked script preferences in `uv run --with` ([#13283](astral-sh/uv#13283)) - Retry streaming downloads on broken pipe errors ([#13281](astral-sh/uv#13281)) - Treat already-installed base environment packages as preferences in `uv run --with` ([#13284](astral-sh/uv#13284)) - Avoid enumerating sources in errors for path Python requests ([#13335](astral-sh/uv#13335)) - Avoid re-creating virtual environment with `--no-sync` ([#13287](astral-sh/uv#13287)) ##### Documentation - Remove outdated description of index strategy ([#13326](astral-sh/uv#13326)) - Update "Viewing the version" docs ([#13241](astral-sh/uv#13241)) ### [`v0.7.2`](https://github.com/astral-sh/uv/blob/HEAD/CHANGELOG.md#072) [Compare Source](astral-sh/uv@0.7.1...0.7.2) ##### Enhancements - Improve trace log for retryable errors ([#13228](astral-sh/uv#13228)) - Use "error" instead of "warning" for self-update message ([#13229](astral-sh/uv#13229)) - Error when `uv version` is used with project-specific flags but no project is found ([#13203](astral-sh/uv#13203)) ##### Bug fixes - Fix incorrect virtual environment invalidation for pre-release Python versions ([#13234](astral-sh/uv#13234)) - Fix patching of `clang` in managed Python sysconfig ([#13237](astral-sh/uv#13237)) - Respect `--project` in `uv version` ([#13230](astral-sh/uv#13230)) ### [`v0.7.1`](https://github.com/astral-sh/uv/blob/HEAD/CHANGELOG.md#071) [Compare Source](astral-sh/uv@0.7.0...0.7.1) ##### Enhancement - Add support for BLAKE2b-256 ([#13204](astral-sh/uv#13204)) ##### Bugfix - Revert fix handling of authentication when encountering redirects ([#13215](astral-sh/uv#13215)) ### [`v0.7.0`](https://github.com/astral-sh/uv/blob/HEAD/CHANGELOG.md#070) [Compare Source](astral-sh/uv@0.6.17...0.7.0) This release contains various changes that improve correctness and user experience, but could break some workflows; many changes have been marked as breaking out of an abundance of caution. We expect most users to be able to upgrade without making changes. ##### Breaking changes - **Update `uv version` to display and update project versions ([#12349](astral-sh/uv#12349 Previously, `uv version` displayed uv's version. Now, `uv version` will display or update the project's version. This interface was [heavily requested](astral-sh/uv#6298) and, after much consideration, we decided that transitioning the top-level command was the best option. Here's a brief example: ```console $ uv init example Initialized project `example` at `./example` $ cd example $ uv version example 0.1.0 $ uv version --bump major example 0.1.0 => 1.0.0 $ uv version --short 1.0.0 ``` If used outside of a project, uv will fallback to showing its own version still: ```console $ uv version warning: failed to read project: No `pyproject.toml` found in current directory or any parent directory running `uv self version` for compatibility with old `uv version` command. this fallback will be removed soon, pass `--preview` to make this an error. uv 0.7.0 (4433f41c9 2025-04-29) ``` As described in the warning, `--preview` can be used to error instead: ```console $ uv version --preview error: No `pyproject.toml` found in current directory or any parent directory ``` The previous functionality of `uv version` was moved to `uv self version`. - **Avoid fallback to subsequent indexes on authentication failure ([#12805](astral-sh/uv#12805 When using the `first-index` strategy (the default), uv will stop searching indexes for a package once it is found on a single index. Previously, uv considered a package as "missing" from an index during authentication failures, such as an HTTP 401 or HTTP 403 (normally, missing packages are represented by an HTTP 404). This behavior was motivated by unusual responses from some package indexes, but reduces the safety of uv's index strategy when authentication fails. Now, uv will consider an authentication failure as a stop-point when searching for a package across indexes. The `index.ignore-error-codes` option can be used to recover the existing behavior, e.g.: ```toml [[tool.uv.index]] name = "pytorch" url = "https://download.pytorch.org/whl/cpu" ignore-error-codes = [401, 403] ``` Since PyTorch's indexes always return a HTTP 403 for missing packages, uv special-cases indexes on the `pytorch.org` domain to ignore that error code by default. - **Require the command in `uvx <name>` to be available in the Python environment ([#11603](astral-sh/uv#11603 Previously, `uvx` would attempt to execute a command even if it was not provided by a Python package. For example, if we presume `foo` is an empty Python package which provides no command, `uvx foo` would invoke the `foo` command on the `PATH` (if present). Now, uv will error early if the `foo` executable is not provided by the requested Python package. This check is not enforced when `--from` is used, so patterns like `uvx --from foo bash -c "..."` are still valid. uv also still allows `uvx foo` where the `foo` executable is provided by a dependency of `foo` instead of `foo` itself, as this is fairly common for packages which depend on a dedicated package for their command-line interface. - **Use index URL instead of package URL for keyring credential lookups ([#12651](astral-sh/uv#12651 When determining credentials for querying a package URL, uv previously sent the full URL to the `keyring` command. However, some keyring plugins expect to receive the *index URL* (which is usually a parent of the package URL). Now, uv requests credentials for the index URL instead. This behavior matches `pip`. - **Remove `--version` from subcommands ([#13108](astral-sh/uv#13108 Previously, uv allowed the `--version` flag on arbitrary subcommands, e.g., `uv run --version`. However, the `--version` flag is useful for other operations since uv is a package manager. Consequently, we've removed the `--version` flag from subcommands — it is only available as `uv --version`. - **Omit Python 3.7 downloads from managed versions ([#13022](astral-sh/uv#13022 Python 3.7 is EOL and not formally supported by uv; however, Python 3.7 was previously available for download on a subset of platforms. - **Reject non-PEP 751 TOML files in install, compile, and export commands ([#13120](astral-sh/uv#13120), [#13119](astral-sh/uv#13119 Previously, uv treated arbitrary `.toml` files passed to commands (e.g., `uv pip install -r foo.toml` or `uv pip compile -o foo.toml`) as `requirements.txt`-formatted files. Now, uv will error instead. If using PEP 751 lockfiles, use the standardized format for custom names instead, e.g., `pylock.foo.toml`. - **Ignore arbitrary Python requests in version files ([#12909](astral-sh/uv#12909 uv allows arbitrary strings to be used for Python version requests, in which they are treated as an executable name to search for in the `PATH`. However, using this form of request in `.python-version` files is non-standard and conflicts with `pyenv-virtualenv` which writes environment names to `.python-version` files. In this release, uv will now ignore requests that are arbitrary strings when found in `.python-version` files. - **Error on unknown dependency object specifiers ([12811](astral-sh/uv#12811 The `[dependency-groups]` entries can include "object specifiers", e.g. `set-phasers-to = ...` in: ```toml [dependency-groups] foo = ["pyparsing"] bar = [{set-phasers-to = "stun"}] ``` However, the only current spec-compliant object specifier is `include-group`. Previously, uv would ignore unknown object specifiers. Now, uv will error. - **Make `--frozen` and `--no-sources` conflicting options ([#12671](astral-sh/uv#12671 Using `--no-sources` always requires a new resolution and `--frozen` will always fail when used with it. Now, this conflict is encoded in the CLI options for clarity. - **Treat empty `UV_PYTHON_INSTALL_DIR` and `UV_TOOL_DIR` as unset ([#12907](astral-sh/uv#12907), [#12905](astral-sh/uv#12905 Previously, these variables were treated as set to the current working directory when set to an empty string. Now, uv will ignore these variables when empty. This matches uv's behavior for other environment variables which configure directories. ##### Enhancements - Disallow mixing requirements across PyTorch indexes ([#13179](astral-sh/uv#13179)) - Add optional managed Python archive download cache ([#12175](astral-sh/uv#12175)) - Add `poetry-core` as a `uv init` build backend option ([#12781](astral-sh/uv#12781)) - Show tag hints when failing to find a compatible wheel in `pylock.toml` ([#13136](astral-sh/uv#13136)) - Report Python versions in `pyvenv.cfg` version mismatch ([#13027](astral-sh/uv#13027)) ##### Bug fixes - Avoid erroring on omitted wheel-only packages in `pylock.toml` ([#13132](astral-sh/uv#13132)) - Fix display name for `uvx --version` ([#13109](astral-sh/uv#13109)) - Restore handling of authentication when encountering redirects ([#13050](astral-sh/uv#13050)) - Respect build options (`--no-binary` et al) in `pylock.toml` ([#13134](astral-sh/uv#13134)) - Use `upload-time` rather than `upload_time` in `uv.lock` ([#13176](astral-sh/uv#13176)) ##### Documentation - Changed `fish` completions append `>>` to overwrite `>` ([#13130](astral-sh/uv#13130)) - Add `pylock.toml` mentions where relevant ([#13115](astral-sh/uv#13115)) - Add ROCm example to the PyTorch guide ([#13200](astral-sh/uv#13200)) - Upgrade PyTorch guide to CUDA 12.8 and PyTorch 2.7 ([#13199](astral-sh/uv#13199)) ### [`v0.6.17`](https://github.com/astral-sh/uv/releases/tag/0.6.17) [Compare Source](astral-sh/uv@0.6.16...0.6.17) #### Release Notes ##### Preview features - Add PyTorch v2.7.0 to GPU backend ([#13072](astral-sh/uv#13072)) ##### Bug fixes - Avoid panic for invalid Python versions ([#13077](astral-sh/uv#13077)) - Block scripts from overwriting `python` ([#13051](astral-sh/uv#13051)) - Check distribution names to handle invalid redirects ([#12917](astral-sh/uv#12917)) - Check for mismatched package and distribution names on resolver thread ([#13088](astral-sh/uv#13088)) - Fix panic with invalid last character in PEP 508 name ([#13105](astral-sh/uv#13105)) - Reject `requires-python` even if not listed on the index page ([#13086](astral-sh/uv#13086)) #### Install uv 0.6.17 ##### Install prebuilt binaries via shell script ```sh curl --proto '=https' --tlsv1.2 -LsSf https://github.com/astral-sh/uv/releases/download/0.6.17/uv-installer.sh | sh ``` ##### Install prebuilt binaries via powershell script ```sh powershell -ExecutionPolicy Bypass -c "irm https://github.com/astral-sh/uv/releases/download/0.6.17/uv-installer.ps1 | iex" ``` #### Download uv 0.6.17 | File | Platform | Checksum | |--------|----------|----------| | [uv-aarch64-apple-darwin.tar.gz](https://github.com/astral-sh/uv/releases/download/0.6.17/uv-aarch64-apple-darwin.tar.gz) | Apple Silicon macOS | [checksum](https://github.com/astral-sh/uv/releases/download/0.6.17/uv-aarch64-apple-darwin.tar.gz.sha256) | | [uv-x86\_64-apple-darwin.tar.gz](https://github.com/astral-sh/uv/releases/download/0.6.17/uv-x86\_64-apple-darwin.tar.gz) | Intel macOS | [checksum](https://github.com/astral-sh/uv/releases/download/0.6.17/uv-x86\_64-apple-darwin.tar.gz.sha256) | | [uv-aarch64-pc-windows-msvc.zip](https://github.com/astral-sh/uv/releases/download/0.6.17/uv-aarch64-pc-windows-msvc.zip) | ARM64 Windows | [checksum](https://github.com/astral-sh/uv/releases/download/0.6.17/uv-aarch64-pc-windows-msvc.zip.sha256) | | [uv-i686-pc-windows-msvc.zip](https://github.com/astral-sh/uv/releases/download/0.6.17/uv-i686-pc-windows-msvc.zip) | x86 Windows | [checksum](https://github.com/astral-sh/uv/releases/download/0.6.17/uv-i686-pc-windows-msvc.zip.sha256) | | [uv-x86\_64-pc-windows-msvc.zip](https://github.com/astral-sh/uv/releases/download/0.6.17/uv-x86\_64-pc-windows-msvc.zip) | x64 Windows | [checksum](https://github.com/astral-sh/uv/releases/download/0.6.17/uv-x86\_64-pc-windows-msvc.zip.sha256) | | [uv-aarch64-unknown-linux-gnu.tar.gz](https://github.com/astral-sh/uv/releases/download/0.6.17/uv-aarch64-unknown-linux-gnu.tar.gz) | ARM64 Linux | [checksum](https://github.com/astral-sh/uv/releases/download/0.6.17/uv-aarch64-unknown-linux-gnu.tar.gz.sha256) | | [uv-i686-unknown-linux-gnu.tar.gz](https://github.com/astral-sh/uv/releases/download/0.6.17/uv-i686-unknown-linux-gnu.tar.gz) | x86 Linux | [checksum](https://github.com/astral-sh/uv/releases/download/0.6.17/uv-i686-unknown-linux-gnu.tar.gz.sha256) | | [uv-powerpc64-unknown-linux-gnu.tar.gz](https://github.com/astral-sh/uv/releases/download/0.6.17/uv-powerpc64-unknown-linux-gnu.tar.gz) | PPC64 Linux | [checksum](https://github.com/astral-sh/uv/releases/download/0.6.17/uv-powerpc64-unknown-linux-gnu.tar.gz.sha256) | | [uv-powerpc64le-unknown-linux-gnu.tar.gz](https://github.com/astral-sh/uv/releases/download/0.6.17/uv-powerpc64le-unknown-linux-gnu.tar.gz) | PPC64LE Linux | [checksum](https://github.com/astral-sh/uv/releases/download/0.6.17/uv-powerpc64le-unknown-linux-gnu.tar.gz.sha256) | | [uv-s390x-unknown-linux-gnu.tar.gz](https://github.com/astral-sh/uv/releases/download/0.6.17/uv-s390x-unknown-linux-gnu.tar.gz) | S390x Linux | [checksum](https://github.com/astral-sh/uv/releases/download/0.6.17/uv-s390x-unknown-linux-gnu.tar.gz.sha256) | | [uv-x86\_64-unknown-linux-gnu.tar.gz](https://github.com/astral-sh/uv/releases/download/0.6.17/uv-x86\_64-unknown-linux-gnu.tar.gz) | x64 Linux | [checksum](https://github.com/astral-sh/uv/releases/download/0.6.17/uv-x86\_64-unknown-linux-gnu.tar.gz.sha256) | | [uv-armv7-unknown-linux-gnueabihf.tar.gz](https://github.com/astral-sh/uv/releases/download/0.6.17/uv-armv7-unknown-linux-gnueabihf.tar.gz) | ARMv7 Linux | [checksum](https://github.com/astral-sh/uv/releases/download/0.6.17/uv-armv7-unknown-linux-gnueabihf.tar.gz.sha256) | | [uv-aarch64-unknown-linux-musl.tar.gz](https://github.com/astral-sh/uv/releases/download/0.6.17/uv-aarch64-unknown-linux-musl.tar.gz) | ARM64 MUSL Linux | [checksum](https://github.com/astral-sh/uv/releases/download/0.6.17/uv-aarch64-unknown-linux-musl.tar.gz.sha256) | | [uv-i686-unknown-linux-musl.tar.gz](https://github.com/astral-sh/uv/releases/download/0.6.17/uv-i686-unknown-linux-musl.tar.gz) | x86 MUSL Linux | [checksum](https://github.com/astral-sh/uv/releases/download/0.6.17/uv-i686-unknown-linux-musl.tar.gz.sha256) | | [uv-x86\_64-unknown-linux-musl.tar.gz](https://github.com/astral-sh/uv/releases/download/0.6.17/uv-x86\_64-unknown-linux-musl.tar.gz) | x64 MUSL Linux | [checksum](https://github.com/astral-sh/uv/releases/download/0.6.17/uv-x86\_64-unknown-linux-musl.tar.gz.sha256) | | [uv-arm-unknown-linux-musleabihf.tar.gz](https://github.com/astral-sh/uv/releases/download/0.6.17/uv-arm-unknown-linux-musleabihf.tar.gz) | ARMv6 MUSL Linux (Hardfloat) | [checksum](https://github.com/astral-sh/uv/releases/download/0.6.17/uv-arm-unknown-linux-musleabihf.tar.gz.sha256) | | [uv-armv7-unknown-linux-musleabihf.tar.gz](https://github.com/astral-sh/uv/releases/download/0.6.17/uv-armv7-unknown-linux-musleabihf.tar.gz) | ARMv7 MUSL Linux | [checksum](https://github.com/astral-sh/uv/releases/download/0.6.17/uv-armv7-unknown-linux-musleabihf.tar.gz.sha256) | </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 force-pushed the zb/tool-run-check branch from 9eca7cb to bc4f4ad Compare February 18, 2025 20:03

zanieb commented Feb 18, 2025

View reviewed changes

crates/uv/src/commands/tool/run.rs Outdated Show resolved Hide resolved

zanieb changed the title ~~Improve executable checks in uvx~~ Require the command in uvx <name> to be available in the Python environment Feb 18, 2025

zanieb marked this pull request as ready for review February 18, 2025 21:30

zanieb commented Feb 18, 2025

View reviewed changes

crates/uv/tests/it/tool_run.rs Show resolved Hide resolved

jtfmumm reviewed Apr 18, 2025

View reviewed changes

jtfmumm approved these changes Apr 18, 2025

View reviewed changes

zanieb added 3 commits April 18, 2025 16:34

Improve executable checks in uvx

ff5b6b5

Fix construction

d5cab42

Review

a7c86bb

zanieb force-pushed the zb/tool-run-check branch from 5a8ca3d to 02e5fb4 Compare April 18, 2025 21:37

zanieb added the breaking A breaking change label Apr 18, 2025

zanieb changed the base branch from main to release/070 April 18, 2025 21:38

zanieb mentioned this pull request Apr 18, 2025

Allow uvx <name> without --from when the normalized executable name matches #12976

Open

Fix rebase

5456abd

zanieb force-pushed the zb/tool-run-check branch from 02e5fb4 to 5456abd Compare April 18, 2025 21:49

zanieb merged commit a75e449 into release/070 Apr 18, 2025
85 checks passed

zanieb deleted the zb/tool-run-check branch April 18, 2025 21:57

BrewTestBot mentioned this pull request Apr 29, 2025

uv 0.7.0 Homebrew/homebrew-core#221925

Merged

neutrinoceros mentioned this pull request Apr 30, 2025

EXP: pin uv<0.7 in bleeding-edge CI neutrinoceros/inifix#414

Closed

Require the command in uvx <name> to be available in the Python environment #11603

Require the command in uvx <name> to be available in the Python environment #11603

Uh oh!

Conversation

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

Uh oh!

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!

Uh oh!

Uh oh!

jtfmumm Apr 18, 2025 • edited Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

jtfmumm Apr 18, 2025 • edited Loading Uh oh! There was an error while loading. Please reload this page.

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!

jtfmumm commented Apr 18, 2025

Uh oh!

Uh oh!

Reviewers

Assignees

Labels

Projects

Milestone

Development

Uh oh!

3 participants

Require the command in `uvx <name>` to be available in the Python environment #11603

Require the command in `uvx <name>` to be available in the Python environment #11603

zanieb commented Feb 18, 2025 •

edited

Loading

jtfmumm Apr 18, 2025 •

edited

Loading

jtfmumm Apr 18, 2025 •

edited

Loading