logoalt Hacker News

woodruffwlast Tuesday at 7:56 PM12 repliesview on HN

This is our first breaking release since March. We’re happy to answer any questions folks have about it.


Replies

simonwlast Tuesday at 8:35 PM

The thing where "uv init" now adds this to pyproject.toml is a bit surprising:

  [project.scripts]
  demo-latest = "demo_latest:main"
What's the rationale for that? My expectation is that few projects would need it.

(I have a GitHub repo that captures differences between uv versions, here's today's upgrade: https://github.com/simonw/uv-init-demos/commit/9111a2bb85741...)

show 1 reply
_diyarlast Tuesday at 8:12 PM

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.

show 1 reply
helltonelast Tuesday at 8:17 PM

How do you think of uv vs pixi?

Follow up: has anyone suggested the projects collaborate or eventually converge?

show 1 reply
Lucasoatolast Tuesday at 8:02 PM

Has anything changed in your day by day work since OpenAI acquisition?

show 1 reply
hallvardlast Tuesday at 8:01 PM

Why (keep) the `uv pip` interface?

show 4 replies
fishgoesblublast Tuesday at 8:21 PM

Bit surprised, and disappointed to not see dynamic field support for the uv build backend in this update. Need it for dynamically getting the version from Git. Is there anything blocking it, or is it just not important enough?

show 1 reply
simonwlast Tuesday at 8:25 PM

What's blocking a 1.0 release at this point?

show 1 reply
brcmthrowawaylast Tuesday at 8:00 PM

Can you stop the --break-system-packages madness?

show 2 replies
carsmainlast Tuesday at 9:39 PM

Do you have any plans to support pip download?

show 2 replies
pytorch_app4last Tuesday at 8:42 PM

[flagged]

uvvuajdlast Tuesday at 8:36 PM

[flagged]