-
Notifications
You must be signed in to change notification settings - Fork 13
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
Issues with installing on Ubuntu #42
Comments
I strongly recommend against chown I'll clarify this in the README but the options I recommend are: pip3 install --editable .[test] Option 2 for development python3 setup.py develop --user
pip3 install --user flake8 ipykernel mypy nbconvert nbformat pep8-naming pytest And for non-development usage:
or Option 2 for users pip3 install . # If in a virtual environment
#or
pip3 install --user . # If not in a virtual environment |
Another option is to use a conda environment. Closing since the suggestion to use a virtual environment or conda is now in the README. |
Thanks! Tried the new instructions with a virtual environment on my Ubuntu box (with /usr/local/lib/python3.8/dist-packages/ owned by root again, as default in an Ubuntu install) and I can confirm it works. |
..just tried to install pycid on my Ubuntu (20.04) system. I ran into some problems following the current instructions, figure I should report them so that they can be improved. The current instructions are:
Minor problems: I had to do
to get some needed python3 components.
More significantly,
did not create a fully working install, but produced a long error message including:
Digging down, the clean solution to this would have been to add the option -t ~/.local/lib/python3.8/ to the pip3 command line, but this does not work, as for some reason --editable is incompatible with using the -t ~/.local/lib/python3.8/ option, see for example here: pypa/pip#4390 . So in terms of updating the pycid installation instructions to help Ubuntu users, I have identified two possible solution paths leading to a clean install:
Solution 1 (not recommended on multiuser systems): change permissions on /usr/local/lib/python3.8/dist-packages/ to make it writable, e.g. do
before running the pip3 install command.
Solution 2: omit the --editable flag and do:
This copies the cloned repository files to ~/.local/lib/python3.8/site-packages/ , so less useful if you want to edit these files in developer mode.
The text was updated successfully, but these errors were encountered: