virtualenv.
If you're doing more than one project on your machine then you need to concern yourself with dependencies across projects. In python the old-school way of doing this is to use virtualenv and pip. These tools get the job done, but they may have some caveats you should be aware of.
Notes
To start using the newly created virtual environment
for python3.6 (the one in the venv36 folder) you need
to run;
source venv36/bin/activate
You can do a very similar thing for the venv37 folder
to active the virtual environment for python3.7.
source venv37/bin/activate
In both situations you can run which python before and
after and you should see a different path.
Feedback? See an issue? Something unclear? Feel free to mention it here.
If you want to be kept up to date, consider getting the newsletter.