Windows??

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

@@ -70,7 +70,7 @@ pub(crate) async fn find(
 
     println!(
         "{}",
-        python.interpreter().sys_executable().simplified_display()
+        uv_fs::absolutize_path(python.interpreter().sys_executable())?.simplified_display()
     );
 
     Ok(ExitStatus::Success)

crates/uv/tests/python_find.rs

@@ -263,6 +263,10 @@ fn python_find_venv() {
     "###);
 
     // We should find it first
+    // TODO(zanieb): On Windows, this has in a different display path for virtual environments which
+    // is super annoying and requires some changes to how we represent working directories in the
+    // test context to resolve.
+    #[cfg(not(windows))]
     uv_snapshot!(context.filters(), context.python_find(), @r###"
     success: true
     exit_code: 0
@@ -273,6 +277,7 @@ fn python_find_venv() {
     "###);
 
     // Even if the `VIRTUAL_ENV` is not set (the test context includes this by default)
+    #[cfg(not(windows))]
     uv_snapshot!(context.filters(), context.python_find().env_remove("VIRTUAL_ENV"), @r###"
     success: true
     exit_code: 0
@@ -321,6 +326,7 @@ fn python_find_venv() {
     "###);
 
     // We should find virtual environments from a child directory
+    #[cfg(not(windows))]
     uv_snapshot!(context.filters(), context.python_find().current_dir(&child_dir).env_remove("VIRTUAL_ENV"), @r###"
     success: true
     exit_code: 0
@@ -339,6 +345,7 @@ fn python_find_venv() {
     ----- stderr -----
     "###);
 
+    #[cfg(not(windows))]
     uv_snapshot!(context.filters(), context.python_find().current_dir(&child_dir).env_remove("VIRTUAL_ENV"), @r###"
     success: true
     exit_code: 0