Jacob Coffee
Jacob Coffee
``` ➜ ./target/debug/uv pip install litestar --dry-run Resolved 22 packages in 584ms Would install 22 packages - msgspec==0.18.6 - rich-click==1.7.3 - pyyaml==6.0.1 - python-dateutil==2.8.2 - httpcore==1.0.3 - polyfactory==2.14.1 - httpx==0.26.0...
Sorry if this is a bad way to get the version? It felt bad, anyway... I'm not sure if we do or can store version at resolution time and use...
Might be cool to have a `dry-run` flag for uninstalling although not native to `pip`
On the failing CI, I had some failures do to order in stdout there... but I'm wondering how we keep it consistent?
Does this look okay? also not 100% sure how to trigger re-downloads to test that bit. Also, if it works out I can write the tests for it ``` uv...
Just for my notes, i am running into an issue where in testing it passes with 2 `$package==$version`, but in CLI usage i get 4 `====` ``` ➜ ./target/debug/uv pip...
sorry ive not wrapped this - i think my remaining issue is the 4 ====, but ive just had surgery so im down for a bit on my hard thinking...
> Instead, I'd love to hear if this would improve or degrade your experience as a user. Moving away from `pip` into some arbitrarily named command would probably be a...
Hi @cesarmg1980 , all yours 🙂
I think the header reflecting largest/most restrictive is right, but I'm out of my comfort zone here @litestar-org/members ?