Mention `uv pip` behavior in build system note (#9586)

xref https://github.com/astral-sh/uv/issues/9518
This commit is contained in:
Zanie Blue 2024-12-02 16:56:46 -06:00 committed by GitHub
parent 81569c47bf
commit c3904a65c4
No known key found for this signature in database
GPG Key ID: B5690EEEBB952194
1 changed files with 2 additions and 2 deletions

View File

@ -116,8 +116,8 @@ with the default build system.
the presence of a `[build-system]` table is not required in other packages. For legacy reasons, the presence of a `[build-system]` table is not required in other packages. For legacy reasons,
if a build system is not defined, then `setuptools.build_meta:__legacy__` is used to build the if a build system is not defined, then `setuptools.build_meta:__legacy__` is used to build the
package. Packages you depend on may not explicitly declare their build system but are still package. Packages you depend on may not explicitly declare their build system but are still
installable. Similarly, if you add a dependency on a local package, uv will always attempt to installable. Similarly, if you add a dependency on a local package or install it with `uv pip`,
build and install it. uv will always attempt to build and install it.
## Project packaging ## Project packaging