Open cheelee opened 4 years ago
Also noted virtualenv was not available as a default for my local Mac's python installation. Had to invoke pip3 install virtualenv first.
Seems like ensuring that my projects are containerized would help to minimize headaches from the vagaries of installation environments.
The alternative is to lift the initial automated setup script to a level which is abstract enough from the installation instance, and use user instructions to ensure that the right conditions exist for a successful setup.
setup.sh makes poor assumptions about the instance machine's python environment - specifically the python version, the availability of pip and virtualenv.
For instance on my Mac, python defaults to python 2.x and for some reason does not support pip for that version. The correct versions to use there would have been python3 and pip3.
Will need to discover best practices for handling these scenarios.