-
Notifications
You must be signed in to change notification settings - Fork 2.3k
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
poetry.masonry.api.build_wheel disregards metadata_directory #1078
Closed
3 tasks done
Labels
area/build-system
Related to PEP 517 packaging (see poetry-core)
kind/feature
Feature requests/implementations
Comments
This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions. |
Still relevant. |
finswimmer
added
kind/feature
Feature requests/implementations
area/build-system
Related to PEP 517 packaging (see poetry-core)
labels
Feb 8, 2020
This issue has been automatically locked since there has not been any recent activity after it was closed. Please open a new issue for related bugs. |
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
Labels
area/build-system
Related to PEP 517 packaging (see poetry-core)
kind/feature
Feature requests/implementations
I am on the latest Poetry version.
I have searched the issues of this repo and believe that this is not a duplicate.
If an exception occurs when executing a command, I executed it again in debug mode (
-vvv
option).OS version and name: Ubuntu 18.04
Poetry version: Poetry 0.12.15
Link of a Gist with the contents of your pyproject.toml file: N/A
Issue
The current implementation of
poetry.masontry.api:build_wheel
does not usemetadata_directory
per PEP-517. This makes it difficult to implement customizations by overridingprepare_metadata_for_build_wheel
since the output files are not actually used in the wheel. For example, the following does not work:The
METADATA
file edited byprepare_metadata_for_build_wheel
is used by pip for the wheel requirements, however the file is not included in the wheel, sincebuild_wheel
seems to generate a new one.The text was updated successfully, but these errors were encountered: