-
-
Notifications
You must be signed in to change notification settings - Fork 13
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
Fall back to build
?
#155
Comments
Hm, we could add an option for choosing your build backend, however I would expect this bug to be fixed soonish – does pinning to |
Thanks, that worked! Should have checked the changelog... I'm still moderately for having an option to switch without reverting to an old (and eventually outdated) version, but I recognize that every option is a maintenance burden. So I won't be offended if this gets closed as wontfix. Thanks for the great tool! |
Just a note that I now need to pin hatchling to 1.26 to avoid generating metadata 2.4, which the twine pinned in the action version 2.8 rejects. |
I'm currently hitting astral-sh/uv#5450 with
uv build
. This reproduces locally and in usingbuild-and-inspect-python-package
(see https://github.com/nipreps/smriprep/actions/runs/12284124195):If I use
pyproject-build
, everything looks as it should:Would it be possible to add a fallback option to use
pyproject-build
for cases where bugs are found inuv build
?The text was updated successfully, but these errors were encountered: