mirror of
https://github.com/astral-sh/uv.git
synced 2025-07-29 16:13:47 +00:00
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:
parent
724a93bfdb
commit
1ccc15e7bb
15 changed files with 636 additions and 124 deletions
|
@ -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::{
|
||||
|
|
Loading…
Add table
Add a link
Reference in a new issue