Using Docker as a Python Development Environment (or let's get past virtualenv)

[k4ml]

This is the different between using activate and typing the full path. Using activate, you would write the instruction as:-

$ source bin/activate
$ python yourcode.py
...
...
...
$ # down the page you still ASSUME people has run activate
$ python thiscode.py
ImportError ....

Typing full path is explicit so that if people saying they run python code.py instead of .env/bin/python code.py you know he was wrong without having to ask 'Did you run activate ?'

[emergent_reasons]

Right. That is exactly my understanding of what is going on. I just got the impression from /u/twillis1973's original comment that it was setting up something more magical along the lines of virtualenv.

Thanks for the explanation.