Error when workspace contains conflicting Python requirements (#10841)
## Summary If members define disjoint Python requirements, we should error. Right now, it seems that it maps to unbounded and leads to weird behavior. Closes https://github.com/astral-sh/uv/issues/10835.
This commit is contained in:
@@ -75,6 +75,11 @@ impl RequiresPython {
|
||||
}
|
||||
})?;
|
||||
|
||||
// If the intersection is empty, return `None`.
|
||||
if range.is_empty() {
|
||||
return None;
|
||||
}
|
||||
|
||||
// Convert back to PEP 440 specifiers.
|
||||
let specifiers = VersionSpecifiers::from_release_only_bounds(range.iter());
|
||||
|
||||
|
||||
Reference in New Issue
Block a user