| ▲ | stephenlf 4 hours ago |
| uv is the backbone of any modern Python library. I’m excited to see improvements. https://stephenlf.dev/blog/python-library-in-2026/ |
|
| ▲ | marknsikora 3 hours ago | parent | next [-] |
| Good article. But the Makefile part should really be replaced by tox as a best practice. Tox even has a uv runner now that will handle setting up all the environments. |
| |
| ▲ | Zizizizz 2 hours ago | parent | next [-] | | I like just or mise tasks as often my python projects contain many other language commands (SQL, docker, pnpm, etc ...). | |
| ▲ | zbentley 3 hours ago | parent | prev [-] | | There’s a bit of a bootstrap problem there in that Tox (and its dependencies) have to be installed first, unless your makefile is calling “uv run tox” or similar. Uv’s standalone nature makes it ideal for bootstrapping projects in a way that tox isn’t. |
|
|
| ▲ | 1aj-187 3 hours ago | parent | prev | next [-] |
| Can uv even be used with C extensions now? |
| |
|
| ▲ | tingletech 3 hours ago | parent | prev | next [-] |
| they just implement the modern PEPs |
| |
| ▲ | woodruffw 2 hours ago | parent [-] | | We do a lot more than that, e.g. how to cache distributions is not defined anywhere within PEPs (and should not be, since it’s a purely internal tool decision). But yes, it helps that uv implements the PEP for detached metadata, particularly during resolution. |
|
|
| ▲ | 310298 3 hours ago | parent | prev [-] |
| Nonsense. uv is one of many existing build tools. All the items can be done by other programs. Funny to list OpenAI as an example at the end of the blog post ... |
