-
Notifications
You must be signed in to change notification settings - Fork 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
Hint at next step, during install, when wheel building fails #6584
Comments
Good call. At the least, maybe a less-ominous sounding beginning than “Failed” could be used so people don’t get the feeling something went horribly wrong (e.g. “Building a wheel didn’t work so ...” maybe also with a “because ....”). |
See also the similar (or same?) #6256. |
It's similar -- in general I think we can improve our error messaging here. |
@pradyunsg Is this still an issue? I tried to replicate it just now and got: Successfully built pycparser Thanks! |
@ei8fdb Yes; the issue is for when the "successfully built" stage fails in your output fails. That failure is fairly system-dependent (eg. missing compiler, missing OS libraries etc). Currently, pip prints "Failed building wheel for <pkg>" and then proceeds to attempt an install via We can discuss pip's build process in more detail over other media (like a voice/video call) if needed. :) |
Perhaps:
Error:
@pradyunsg is this accurate? Would something like this be possible? |
ref: https://stackoverflow.com/questions/53204916/what-is-the-meaning-of-failed-building-wheel-for-x-in-pip-install
When pip fails to build a wheel, the message is a little mysterious for the users. It might be a good idea to see how we can enhance that to be "better".
Note that pip wheel uses the same code, so we should consider that here as well.
The text was updated successfully, but these errors were encountered: