Fix: force pyo3 to pick up the virtual environment generated by uv rather than system Python

Author: LukeMathWalker

.wr.toml

@@ -1,13 +1,3 @@
 [[verification]]
 command = "cargo"
-args = ["test"]
-
-[[verification]]
-command = "uv"
-# We use `--all-packages` to avoid having to specify `pytest` as a dev
-# dependency in all packages.
-args = ["sync", "--all-packages"]
-
-[[verification]]
-command = "uv"
-args = ["run", "pytest"]
+args = ["run", "--package", "verifier", "--bin", "verifier"]

Cargo.lock

@@ -1,9 +1,10 @@
 [workspace]
-members = ["exercises/*/*"]
+members = ["exercises/*/*", "verifier"]
 resolver = "2"
 
 [workspace.dependencies]
 anyhow = "1"
+duct = "0.13"
 pyo3 = "0.23.3"
 semver = "1.0.23"
 serde = "1.0.204"

Cargo.toml

@@ -0,0 +1,7 @@
+[package]
+name = "verifier"
+version = "0.1.0"
+edition = "2021"
+
+[dependencies]
+duct = { workspace = true }

verifier/Cargo.toml

@@ -0,0 +1,19 @@
+use duct::cmd;
+
+fn main() -> Result<(), Box<dyn std::error::Error>> {
+    // Create the project-specific Python virtual environment.
+    println!("Creating the Python virtual environment...");
+    cmd!("uv", "sync", "--all-packages").run()?;
+
+    println!("Testing the Rust crate...");
+    let venv = std::env::current_dir()?.join(".venv");
+    cmd!("cargo", "test")
+        // Tell `pyo3` where to find the project-specific
+        // virtual environment.
+        .env("VIRTUAL_ENV", venv)
+        .run()?;
+    println!("Testing the Python package...");
+    cmd!("uv", "run", "pytest").run()?;
+
+    Ok(())
+}