Move installable targets out of uv-resolver crate (#10126)

## Summary

The proximate motivation is that I want to add new variant for scripts,
but `uv-resolver` can't depend on `uv-scripts` without creating a
circular dependency. However, I think this _does_ just make more sense
-- the resolver crate shouldn't be coupled to the various kinds of
workspaces, and these details are mostly encoded in `projects/lock.rs`
and similar files.
This commit is contained in:
Charlie Marsh 2024-12-24 19:01:50 -05:00 committed by GitHub
parent 6745a8b00a
commit 7c47a457d9
No known key found for this signature in database
GPG key ID: B5690EEEBB952194
11 changed files with 116 additions and 84 deletions

View file

@ -5,7 +5,7 @@ pub use exclusions::Exclusions;
pub use flat_index::{FlatDistributions, FlatIndex};
pub use fork_strategy::ForkStrategy;
pub use lock::{
InstallTarget, Lock, LockError, LockVersion, PackageMap, RequirementsTxtExport,
Installable, Lock, LockError, LockVersion, Package, PackageMap, RequirementsTxtExport,
ResolverManifest, SatisfiesResult, TreeDisplay, VERSION,
};
pub use manifest::Manifest;