Closed Huge closed 3 years ago
further I tried mkdir mySetup2 && python3 setup.py install --prefix=mySetup2 && mySetup2/bin/shamir
with the same result.
you're installing the package outside your PYTHONPATH
. use export PYTHONPATH=/path/to/mySetup/lib/python3.8/site-packages
to make it work.
the recommended way is actually to not mess with --install-dir
and instead install into a virtualenv
Thankful for the explanation, though I'd have appreciated the README to mention this is the recommended way for tweaking the code. Also a requirements.txt
list would come handy to facilitate the venv workflow.
you could accomplish the same with pip install -e .
inside the virtualenv; the requirements are expressed inside setup.py
. It might be better to use pip install -e .
instead of python setup.py develop
in the README for this reason. We'll accept a PR for the readme; unfortunately, it's not realistic to include full step-by-step instructions for all the possible configurations of the user's environment, so they'll need to gather some knowledge about this on their own.
I cloned the repo and went to install from the checkout as README says, this way:
mkdir mySetup/ && python3 setup.py develop --install-dir=mySetup/
which went ok. After that./mySetup/shamir
executes with following error:Side note:
pipx install
might be worth recommending as that worked well for me exploring the cli. Although I have some trouble to inspect the code 'live' from the repo.