Include WHEEL metadata when using PDM and poetry backends #2881
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
When building a
wheel
oreditable
package with a PEP 517 backend, no longer pass an emptymetadata_directory
to the backendbuild_wheel
orbuild_editable
endpoint.Some backends, such as PDM and poetry, will not generate package metadata in the presence of a
metadata_directory
, even if it is empty.Prior to this change, attempting to install a wheel created by tox using PDM or poetry would return an error like
There is no item named 'my-package.0.1.dist-info/WHEEL' in the archive
Fix #2880
Fix #2870
Thanks for contribution
Please, make sure you address all the checklists (for details on how see
development documentation)!
tox -e fix
)docs/changelog
folder