-
Notifications
You must be signed in to change notification settings - Fork 8
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
Error when installing a wheel on Windows #10
Comments
A different failure:
NB: I changed the final This time buildout actually installed an |
@lelit I have a similar problem to the second issue you report here. In my case with PyYAML. I think the root cause is the non-lowercase package name. I can reproduce a failure with the same stack trace:
In my case this reproduces even when I comment out the
in my I have a small change to buildout which fixes this, am going to try to make a PR for that too. Can you try this change to the Change this function (line 1648):
to add a call to
|
That issue (discussed above) has now been reported independently to the buildout project. See buildout/buildout#385. There is some suggestion that this should perhaps be fixed in |
Thank you. I'm sorry but it's unlikely I will be able to try your suggestion [soon enough] as I'm deeply focused on other project these days. |
@daybarr I can confirm that your changes resolve this issue for me. Are you still willing to put together a pull request? |
I'm using Python 3.6.1, zc.buildout 2.9.3 and buildout.wheel 0.2.0.
I activated the buildout.wheel extension and tried to build an application that needs binary distributions; for each downloaded wheel, buildout errors out the following traceback:
Apparently the wheel got installed under
eggs/reportlab-3.4.0-cp36-cp36m-win32.ovo
, and indeed re-executing the buildout it goes on fetching the remaining packages, failing again on the next wheel.The text was updated successfully, but these errors were encountered: