astral-sh/uv

Add Windows unit test coverage to `uv-interpreter` discovery

Open

#3709 opened on May 21, 2024

View on GitHub
 (0 comments) (0 reactions) (0 assignees)Rust (84,934 stars) (3,111 forks)batch import
help wantedtestingwindows

Description

Follow-up to https://github.com/astral-sh/uv/pull/3266

Our mock interpreters only work on Unix, so we don't have good Windows test coverage for interpreter discovery behavior. We should build a mock interpreter utility for Windows.

Contributor guide

Tech stack
rustpython
Domain
testingdeveloper experience
Issue type
test
DifficultyEstimated implementation difficulty for a new contributor, from 1 for very small changes to 5 for expert-level work.
3
Estimated timeA rough time range for an experienced contributor to investigate, implement, test, and prepare a pull request.
half day
Activity statusHow available the issue appears right now: fresh, active, stale, blocked, or waiting on maintainer input.
fresh
ClarityHow clearly the issue explains the expected change, acceptance criteria, and next step.
mostly clear
Prerequisites
RustWindows OSunit testing concepts
Newbie friendlinessA 1-100 score estimating how approachable this issue is for first-time contributors.
60
Research direction
Review the existing Unix mock interpreter implementation from PR #3266 (https://github.com/astral sh/uv/pull/3266). Understand how it works and identify the Windows specific differences (e.g., file paths, environment variables). Create a similar mock utility for Windows in the test directory, following the same patterns. Consider using conditional compilation (#[cfg(windows)]) to isolate Windows specific code. Ensure the new utility can be used to test interpreter discovery on Windows CI.