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
Regression in hatchling 1.12.0: some optional config_settings became mandatory #691
Comments
musicinmybrain
added a commit
to musicinmybrain/hatch
that referenced
this issue
Dec 31, 2022
Oh darn sorry about that |
No worries! This regression is an easy fix, and the improvements in this release are really nice. Thanks for taking a look at it. |
ofek
added a commit
that referenced
this issue
Dec 31, 2022
* Restore missing default for config_settings Fixes #691 * fix Co-authored-by: Ofek Lev <ofekmeister@gmail.com>
I actually just introduced some scripts that make it easier to release, I will release it in a few moments 🙂 |
https://github.com/pypa/hatch/releases/tag/hatchling-v1.12.1 Thanks for the report and the fix! |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
When type annotations were added to
backend/src/hatchling/build.py
in 7b9c12d, several functions with aconfig_settings=None
parameter lost the default value, makingconfig_settings
mandatory:get_requires_for_build_editable
build_editable
prepare_metadata_for_build_wheel
prepare_metadata_for_build_editable
The same thing happened to
get_requires_for_build_editable
inbackend/src/hatchling/ouroboros.py
.This breaks Fedora Linux’s use of the
prepare_metadata_for_build_wheel
hook (#128) to generate dependencies when building RPMs from Python packages that use hatchling, which has worked since #466.I think this change was an accident.
The text was updated successfully, but these errors were encountered: