The default it had to build
The build instructions uv writes into every new Python project now name a builder Astral wrote itself, and that alone was enough to bring back a default the company had deleted.
Run uv's project setup command in version 0.12.0, out on 28 July, and it no longer leaves a lone starter file in an empty folder. Your code goes into a folder one level down, a command name other people can type gets registered, and a short block appears naming the program that will turn the whole thing into something installable. That program is Astral's own, and it was already sitting inside the executable you just ran.
Astral could not restore the recommendation until it owned the program the recommendation names.
The last part is why the default exists at all. Astral shipped this same layout in an early version of uv and pulled it back out one release later, because the block it generated named hatchling, a separate build program that people arriving at Python had never heard of and were suddenly asked to download and trust. Rather than keep arguing for the layout, Astral wrote a builder of its own and folded it into uv, so the generated file now points at something the reader already has. The recommendation returned the moment naming it cost nothing.
That builder handles pure Python and nothing else. Projects that mix in C or Rust for speed, which covers most of the scientific and machine-learning stack, still have to edit that line to name an older tool. The new default therefore sorts fresh projects into two kinds on their first day: the ones uv can build end to end, and the ones that reach back outside it.
Whether to bury your code one folder deeper has been argued in Python blog posts for a decade and has stayed a minority habit, because the whole cost lands on day one, when a new project is the last thing anyone wants to think carefully about. Anyone who wants the flat version types the setup command with a no-package flag and gets it. Everyone who types nothing now gets the layout the ecosystem spent that decade failing to talk people into.
"The uv build backend currently only supports pure Python code." — Astral's uv documentation
Run uv init on a throwaway name and open the pyproject.toml it writes; the backend doc walks through what that build-system block actually does and how to swap it for something else.
Get the tool at docs.astral.sh →The lenses
The facts
Concepts
How this connects
Tap a node to open it