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. |
||
|---|---|---|
| .. | ||
| bench | ||
| benchmarks | ||
| bootstrap | ||
| packages | ||
| popular_packages | ||
| release | ||
| requirements | ||
| scenarios | ||
| wheels | ||
| check_system_python.py | ||
| transform_readme.py | ||