-
Notifications
You must be signed in to change notification settings - Fork 18
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
Install grumpy-tools before building grumpy-runtime #140
Conversation
This still doesn't fix the error.
But then it still fails with error.
|
Thanks for your contribution. The tests are not passing with Go=stable. Would you mind do also fix this before the merge? |
Looks like Python build environment that is set for |
|
Reported the issue upstream in The workaround for now is to serialize and pass |
Passing
|
Trying to forcefully inject just a single build path Maybe parent |
@alanjds ready for review. Install works ok.
|
`pip2 install grumpy-runtime` fails with the ERROR grumpyhome#113 (comment) because it relies on `grumpy-tools`. `grumpy-tools` packages is specified in `setup.py` as a dependency, and it doesn't work, because for the build process to succeed, the dependency should already exist at the time `setup.py` is executed. The official workaround is `pyproject.toml` from PEP-518 pypa/pip#2381
Necessary to locate `grumpy-tools` when building wheel for runtime during `pip install`.
8934362
to
9d26049
Compare
Thanks @abitrolly. I bet this was a pain to tackle. |
Took quite a bit a time, indeed. |
pip2 install grumpy-runtime
fails with the ERROR#113 (comment)
because it relies on
grumpy-tools
.grumpy-tools
packages is specified insetup.py
as adependency, and it doesn't work, because for the build process to
succeed, the dependency should already exist at the time
setup.py
is executed.
The official workaround is
pyproject.toml
from PEP-518pypa/pip#2381