Charlie Marsh 5270624b11 Avoid prepare_metadata_for_build_wheel calls for Hatch packages with dynamic dependencies (#2645) ... ## 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.		2024-03-25 22:26:51 +00:00
..
src	Avoid prepare_metadata_for_build_wheel calls for Hatch packages with dynamic dependencies (#2645)	2024-03-25 22:26:51 +00:00
.gitignore	Rename to uv (#1302)	2024-02-15 11:19:46 -06:00
Cargo.toml	Avoid repeating paths of workspace packages (#2573)	2024-03-20 16:16:02 -04:00