-
Notifications
You must be signed in to change notification settings - Fork 22
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
Build fails #45
Comments
Please check with #46 |
Hi @GMishx , Thanks. I checked out your branch, and when I run
However, if I install the requirements first ( |
Before building Atarashi, you need to install the dependencies. You can install either through I forgot to add it to the README |
I think it has been added to the readme @robguinness if you would like to help us, you could consider confirming it is working and we could merge the PR. |
There is a mention of |
Sorry, I'm actually getting another issue now when trying to build:
It seems this is a similar issue as above, except now it is related to building the dependency |
I have opened another PR #48. It implements PEP 518 to install dependencies. Can you please test it @robguinness? Hope this will work for you. |
Great! I will test this tomorrow, as it's getting late here. |
The installation goes through with no errors, but when I try to run the program, e.g.:
I get a
So it seems that somewhere the path to the license files is configured incorrectly, since these files are not copied to site-packages. |
😨 I anticipated this but it did not occurred with me. Anyway, let me check. |
Hey, have you tried the new commit I pushed to #48? It worked for me in a virtual environment and as a standard install as well. |
I get a new error:
|
Thank you for your patience @robguinness ! |
Hi! Sorry for the delays. I got pulled in other directions. I'm trying to get back to this work this week, and I will update you when I've tried it. Thanks for YOUR patience! ;-) |
Hi, I'm getting an error when trying to build (master branch) on Python 3.7:
I'm able to build when I run the command with sudo, but this shouldn't be necessary per my understanding.
The text was updated successfully, but these errors were encountered: