Use correct ordering semantics for narrowing upper-bounded Python requirements (#7031)

## Summary

We need to use different ordering semantics for upper and lower Python
bounds.

Closes https://github.com/astral-sh/uv/issues/6911.
This commit is contained in:
Charlie Marsh 2024-09-04 11:57:14 -04:00 committed by GitHub
parent 724a93bfdb
commit 1ccc15e7bb
No known key found for this signature in database
GPG key ID: B5690EEEBB952194
15 changed files with 636 additions and 124 deletions

View file

@ -12,9 +12,7 @@ pub use preferences::{Preference, PreferenceError, Preferences};
pub use prerelease::PrereleaseMode;
pub use pubgrub::{PubGrubSpecifier, PubGrubSpecifierError};
pub use python_requirement::PythonRequirement;
pub use requires_python::{
RequiresPython, RequiresPythonBound, RequiresPythonError, RequiresPythonRange,
};
pub use requires_python::{RequiresPython, RequiresPythonError, RequiresPythonRange};
pub use resolution::{AnnotationStyle, DisplayResolutionGraph, ResolutionGraph};
pub use resolution_mode::ResolutionMode;
pub use resolver::{