I've been endeavoring to have a single make setup command take care of nearly everything to get ACCEPT up and running. At the moment, however, you still have to type a pip command to get the driver's Python dependencies.
The tricky bit here is that pip needs to be invoked differently on different systems if we're going to distribute dependencies that way (i.e., with or without sudo and with or without --user). Maybe we should install into a virtualenv?
We could package the accept driver bit as a normal Python package (i.e., with a setup.py that declares the dependencies).
We should also probably not include the dependencies of the eval.py scripts, which requirements.txt currently does include. Those can be installed separately.
According to Luyi's machine, the Pillow dependency is sort of broken. Another argument for removing the app-specific dependencies from requirements.txt.
I've been endeavoring to have a single
make setup
command take care of nearly everything to get ACCEPT up and running. At the moment, however, you still have to type apip
command to get the driver's Python dependencies.The tricky bit here is that
pip
needs to be invoked differently on different systems if we're going to distribute dependencies that way (i.e., with or withoutsudo
and with or without--user
). Maybe we should install into a virtualenv?We could package the
accept
driver bit as a normal Python package (i.e., with a setup.py that declares the dependencies).We should also probably not include the dependencies of the eval.py scripts, which
requirements.txt
currently does include. Those can be installed separately.