-
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
aeneas build fails in Poetry, succeeds with pip wheel --use-pep517 #8462
Comments
per the error message you'll need to report this to aeneas: that package does not support pep517 builds since their last release was in 2017 I don't much like your chances, but there's nothing that poetry can do about that. |
Thanks for the response. I imagine the earlier issue I found with the homebrew path I would hit after this. Looks like someone else has already hit this numpy issue and submitted a PR to fix. Thanks for reading it. The only confusing part about your message is that with the provided environment variable it did build with pep517 in a completely new virtualenv. But I imagine what I'm hitting is part of https://peps.python.org/pep-0518/#build-system-table
Not sure why it's different than what Poetry is doing. My only thought is that numpy isn't available for some reason in the Poetry install version compared to the pip build?
|
Nevermind!
Do you think a PR adding |
(it's the cached aeneas wheel that pip is using, the cached numpy wheel is irrelevant.) sure, a merge request adding that parameter sounds sensible: it would have saved you and me some time today, it can save someone else some time tomorrow |
When trying to determine if the issue was because of Poetry or the package not supporting PEP-517 mode, it is possible that the pip cache can result in false positives of packages that support PEP-517. An example of this is the issue python-poetry#8462. This PR adds to the error output and recommended command to prevent this from happening in the future. As a new user to Python, it wasn't immediately obvious to me when running on the command line why it succeeded, and simply took that it did as enough confirmation that opening an issue was valid.
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. |
-vvv
option) and have included the output below.Issue
As indicated above, I found that setting
LIBRARY_PATH=/opt/homebrew/lib
was a requirement forpip wheel --use-pep517 "aeneas (==1.7.3.0)"'
to succeed due to/opt/homebrew/lib
not being passed via the aeneas build.However, setting that here, building this still doesn't succeed.
The error comes from the following:
https://github.com/readbeyond/aeneas/blob/v1.7.3/setup.py#L188-L195
The text was updated successfully, but these errors were encountered: