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

  [project.scripts]
  demo-latest = "demo_latest:main"

(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...)

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.

How do you think of uv vs pixi?

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

Why (keep) the `uv pip` interface?

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

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?

What's blocking a 1.0 release at this point?

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

[flagged]

[flagged]