11–20 of 51 posts
This is our first breaking release since March. We’re happy to answer any questions folks have about it.
Can you stop the --break-system-packages madness?
This is our first breaking release since March. We’re happy to answer any questions folks have about it.
Earlier quoted context omitted.
Why (keep) the `uv pip` interface?
We have the interface because we care a lot about meeting people where they are. We keep the interface because we care a lot about long-term support and compatibility. I cannot imagine removing it. We generally want to add features to the top-level interface such that people don't need or want to use the pip-interface because the top-level interface does everything you need, but better.
And of course that some colleagues of mine insist on using `uv pip` for anything and everything, which feels wrong…
Granted it’s a great feature which made the transition to uv smooth in the first place.
This is our first breaking release since March. We’re happy to answer any questions folks have about it.
Follow up: has anyone suggested the projects collaborate or eventually converge?
This is our first breaking release since March. We’re happy to answer any questions folks have about it.
Maybe a naive question, but any goal / progress towards an ”it just works” cuda installation? Currently, the only times i feel like i‘m stumbling over an install with uv is when pytorch / cuda is involved.
There are two PEPs that we're involved with that will provide the components for the ecosystem to properly declare metadata in this domain [1] [2].
We're also working on some features in uv, such as the torch backend option [3], to improve the situation in the interim.
We'll be announcing more in this area in the near future!
[1] https://peps.python.org/pep-0817/ [2] https://peps.python.org/pep-0825/ [3] https://docs.astral.sh/uv/guides/integration/pytorch/#automa...
This is our first breaking release since March. We’re happy to answer any questions folks have about it.