-
Notifications
You must be signed in to change notification settings - Fork 43
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
Incompatible dependencies #421
Comments
python3.8 does not have this dependency conflict so does the project need to up its python dependency requirement? |
Can you try updating flake8? It's just a development dependency without version pin... |
it installs but I get an error warning me
|
Ok. The version pin was added because of this issue python/importlib_metadata#411 which caused builds to fail on 3.7. Can you please try what happens when you remove the version pin in Web API? |
I don't get a dependency conflict when I remove the pin from the setup.py. pip says it now has 4.2.0 of importlib-metadata installed |
Cool, perhaps the bug has been fixed. Do you want to submit a PR? |
I am still having precommit issues. Trying to resolve that is how I ran into this. :) |
You'll have to check me because I just did --no-verify |
Fixed by #422. |
There is a dependency conflict when trying to install grapmps-webapi dependencies.
Did the following to get this issue on Linux Mint:
Once repository is cloned
In grapmps-webapi project root setup a new virtual environment set to python 3.7 and activate environment. I used pyenv with pyenv-virtualenv plugin
Edit your virtual environments pyvenv.cfg file (for me it was in ~/.pyenv/versions//pyvenv.cfg) to set
include-system-site-packages
toTrue
and save.Install dev dependencies
pip install -r requirements-dev.txt
Install gramps-webapi and dependencies
pip3 install -e .
This should create the conflict error listed above. Not using --user on the editable dependency install because it in the virtual environment it would create a lack of sys.path precedence to gramps-webapi (see pypa/pip#573)
The text was updated successfully, but these errors were encountered: