Consider having a script that automagically creates a python virtualenv for you and loads the package requirements. A small but useful thing to keep the user's python environment 'clean'. I have a small project that I use this script for:
#
# bootstrap the virtual env if necessary
#
if [ -f "v/bin/activate" ]
then
echo virtual env already created
source v/bin/activate
else
virtualenv v
source v/bin/activate
fi
# Just install dependencies by default to pick up any changes
pip install jinja2
pip install jsl
pip install jsonschema
pip install rethinkdb
#
# run the data server
#
python ucdataserver.py
Where I explicitly invoke pip install you could use the requirements.txt file instead.
Consider having a script that automagically creates a python virtualenv for you and loads the package requirements. A small but useful thing to keep the user's python environment 'clean'. I have a small project that I use this script for:
Where I explicitly invoke pip install you could use the requirements.txt file instead.