Hacker News Board Hacker News, browsed like a classic message board
Live data from Hacker News

Uv 0.12.0

github.com

Post reply on HN
Print view View original

31–40 of 51 posts

Re: Uv 0.12.0

#32

Post by zanie »

simonw wrote: post #30
woodruffw wrote: post #2

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

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

It makes `uv run ` work by default, I expect most projects to need an entry point.

Re: Uv 0.12.0

#35

Post by gkhartman »

walthamstow wrote: post #20
hallvard wrote: post #5

Earlier quoted context omitted.

Why (keep) the `uv pip` interface?

uv pip is a brilliant adoption gateway, you get all of the speed gains for a 3 char change

Yeah, I don't think I'd have made the jump otherwise, since convincing others on the team would have been much harder.

Re: Uv 0.12.0

#36

Post by XorNot »

Are we likely to get an "uv upgrade" command that makes sense sometime?

It's still very obtuse how to get uv to just try and make all my dependencies the highest version possible.

Re: Uv 0.12.0

#37

Post by EuanReid »

zanie wrote: post #27
nvme0n1p1 wrote: post #22

Earlier quoted context omitted.

Laudable goals. Have you considered gating imperative commands behind a setting, maybe `tool.uv.pip.unreproducible = true` or somesuch? This would gently guide people towards better workflows, and also be a starting point for documenting the drawbacks of `uv pip` since it's a setting they'd be forced to add and presumably they'll read the docs for it first. uv already does something similar with `tool.uv.pip.break-sy…

I hadn't considered that, it's an interesting idea. We generally hold a very high bar for nagging users or gating behaviors. It's possible we'll reach a point someday where this is appropriate! I think you're right that we need to teach people better workflows, but that's happening organically as use of the tool grows and people's first exposure to a Python project is `uv init` and `uv add` rather than `pip`.

Perhaps something requiring opt-in sooner, so project maintainers can - through config - say "we don't use the pip interface on this project"?

Re: Uv 0.12.0

#38

Post by ghshephard »

hallvard wrote: post #5
woodruffw wrote: post #2

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

Why (keep) the `uv pip` interface?

I'll confess to using `uv` almost every day for the last year+ - and I've never used anything other than `uv pip install` for package management.

Is there any compelling reason not to?

Re: Uv 0.12.0

#39

Post by peterdsharpe »

XorNot wrote: post #36

Are we likely to get an "uv upgrade" command that makes sense sometime? It's still very obtuse how to get uv to just try and make all my dependencies the highest version possible.

`uv sync --upgrade`? It's in the docs
Post reply on HN