Allow users to specify a custom package spec to uv tool run

crates/uv/src/cli.rs

@@ -1945,6 +1945,11 @@ pub(crate) struct ToolRunArgs {
     #[arg(allow_hyphen_values = true)]
     pub(crate) args: Vec<OsString>,
 
+    // TODO(zanieb): Consider using `Vec<String>` instead, treating the first as the target package
+    /// Use the given package specification instead of inferring it from the target command.
+    #[arg(long)]
+    pub(crate) package: Option<String>,
+
     /// The Python interpreter to use to build the run environment.
     #[arg(
         long,

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

@@ -23,6 +23,7 @@ pub(crate) async fn run(
     target: String,
     args: Vec<OsString>,
     python: Option<String>,
+    package: Option<String>,
     _isolated: bool,
     preview: PreviewMode,
     cache: &Cache,
@@ -32,9 +33,10 @@ pub(crate) async fn run(
         warn_user!("`uv tool run` is experimental and may change without warning.");
     }
 
-    // TODO(zanieb): Allow users to pass an explicit package name different than the target
-    // as well as additional requirements
-    let requirements = [RequirementsSource::from_package(target.clone())];
+    // TODO(zanieb): Allow users to pass additional requirements
+    let requirements = [RequirementsSource::from_package(
+        package.unwrap_or_else(|| target.clone()),
+    )];
 
     // TODO(zanieb): When implementing project-level tools, discover the project and check if it has the tool
     // TOOD(zanieb): Determine if we sould layer on top of the project environment if it is present

crates/uv/src/main.rs

@@ -607,6 +607,7 @@ async fn run() -> Result<ExitStatus> {
                 args.target,
                 args.args,
                 args.python,
+                args.package,
                 globals.isolated,
                 globals.preview,
                 &cache,