Tim de Jager eaf517efd8 Add method to get packages involved in a `NoSolutionError` (#14457) ... <!-- Thank you for contributing to uv! To help us out with reviewing, please consider the following: - Does this pull request include a summary of the change? (See below.) - Does this pull request include a descriptive title? - Does this pull request include references to any relevant issues? --> ## Summary <!-- What's the purpose of the change? What does it do, and why? --> In pixi we overlay the PyPI packages over the conda packages and we sometimes need to figure out what PyPI packages are involved in the no-solution error. We could parse the error message, but this is pretty error-prone, so it would be good to get access to more information. A lot of information in this module is private and should probably stay this way, but package names are easy enough to expose. This would help us a lot! I collect into a HashSet to remove duplication, and did not want to expose a rustc_hash datastructure directly, thats's why I've chosen to expose as an iterator :) Let me know if any changes need to be done, and thanks! --------- Co-authored-by: Zanie Blue <contact@zanie.dev>		2025-07-04 18:08:23 +00:00
..
src	Add method to get packages involved in a `NoSolutionError` (#14457)	2025-07-04 18:08:23 +00:00
Cargo.toml	Add `DisplaySafeUrl` newtype to prevent leaking of credentials by default (#13560)	2025-05-27 00:05:30 +02:00