mirror of https://github.com/astral-sh/uv
5270624b11
## Summary Hatch allows for highly dynamic customization of metadata via hooks. In such cases, Hatch can't upload the PEP 517 contract, in that the metadata Hatch would return by `prepare_metadata_for_build_wheel` isn't guaranteed to match that of the built wheel. Hatch disables `prepare_metadata_for_build_wheel` entirely for pip. We'll instead disable it on our end when metadata is defined as "dynamic" in the pyproject.toml, which should allow us to leverage the hook in _most_ cases while still avoiding incorrect metadata for the remaining cases. Closes: https://github.com/astral-sh/uv/issues/2130. |
||
|---|---|---|
| .. | ||
| black_editable | ||
| deptry_reproducer | ||
| hatchling_dynamic | ||
| hatchling_editable | ||
| maturin_editable | ||
| poetry_editable | ||
| root_editable | ||
| setup_cfg_editable | ||
| setup_py_editable | ||
| setuptools_editable | ||
| README | ||
README
# packages A collection of packages used to test editable installs and bespoke behaviors in packaging setups and definitions.