From 04c4da4e65d61347a19960f1ba94cc26d4d01458 Mon Sep 17 00:00:00 2001 From: Charlie Marsh Date: Mon, 10 Jun 2024 06:28:33 -0700 Subject: [PATCH] Fix `>=` to `==` typo in `is_contained_by` docs (#4196) --- crates/uv-resolver/src/requires_python.rs | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/crates/uv-resolver/src/requires_python.rs b/crates/uv-resolver/src/requires_python.rs index c5706ebc6d80..226242e7f8d8 100644 --- a/crates/uv-resolver/src/requires_python.rs +++ b/crates/uv-resolver/src/requires_python.rs @@ -127,7 +127,7 @@ impl RequiresPython { // does not. But, it's debatable. // // If this scheme proves problematic, we could explore using different semantics when - // converting to PubGrub. For example, we could parse `>=3.8.*` as `>=3.8,<3.9`. But this + // converting to PubGrub. For example, we could parse `==3.8.*` as `>=3.8,<3.9`. But this // too could be problematic. Imagine that the user requests `>=3.8.0b0`, and the target // declares `==3.8.*`. In this case, we _do_ want to allow resolution, because the target // is saying it supports all versions of `3.8`, including pre-releases. But under those