-
Notifications
You must be signed in to change notification settings - Fork 1.2k
Add uv-build to table #1880
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
base: main
Are you sure you want to change the base?
Add uv-build to table #1880
Conversation
I'm happy to add uv-build in the other locations mentioned in the linked issue. Is it OK in this PR, or should I open a new one? |
Head branch was pushed to by a user without write access
for more information, see https://pre-commit.ci
I think it's easy enough to add this here. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I noticed that the table in writing-pyproject-toml.rst
lists hatchling 1.27.0, whereas build-backend-tabs.rst
contains 1.26.0. Should I fix this and if so, which one is the correct version?
It's probably a good idea to separate such changes. Also, the broken link needs a separate PR too, to unblock this. |
.. code-block:: toml | ||
|
||
[build-system] | ||
requires = ["uv_build >= 0.7.19, <0.9.0"] |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Upper limits are normally discouraged. What's the justification here?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
See the note in their official docs: https://docs.astral.sh/uv/concepts/build-backend/#using-the-uv-build-backend
uv-build is stable since 0.7.19 and supports PEP 639.
📚 Documentation preview 📚: https://python-packaging-user-guide--1880.org.readthedocs.build/en/1880/