On Wed, 9 Jan 2019 at 19:25, Mark Sapiro <mark@msapiro.net> wrote:
On 1/8/19 10:50 PM, Odhiambo Washington wrote:
Now that has clarified the matter for me. That even when I am logged out, the scripts do the neccessary to activate the venv to run things.
As mentioned before, a virtualenv is not like a container. It is only a directory that contains among other things a bin/ directory with activate scripts and easy_install, python, pip and wheel commands.
When you activate a virtualenv in your shell, all it really does is add a deactivate command, modify the command prompt and insert its bin/ directory at the beginning of its PATH.
What this means is whether or not a virtualenv is "active", running a command from the bin/ directory in the virtualenv is using the virtualenv.
Thank you very much for the elaboration. What used to confuse me was the early stage documents which detailed how to run MM3 in a virtual environment - I am talking about the BETA days. I think from this point onward, I have the complete foundation information to move forward.
-- Best regards, Odhiambo WASHINGTON, Nairobi,KE +254 7 3200 0004/+254 7 2274 3223 "Oh, the cruft.", grep ^[^#] :-)