Note that there are some explanatory texts on larger screens.

plurals
  1. PO
    text
    copied!<p>If you've already installed virtualenv like this:</p> <pre><code>pip install virtualenv </code></pre> <p>You'll then want to setup a particular virtualenv folder:</p> <pre><code>virtualenv [your project folder name] </code></pre> <p>This will create that project folder with a few important subdirectories.</p> <p>You'll activate your virtualenv first before installing anything new, the newly installed modules will be available to you only when 'sourced' into your virtualenv. From your project folder type:</p> <pre><code>source bin/activate </code></pre> <p>You then will see your virtualenv name in parenthesis on each terminal line. This indicates you are 'sourced' in. NOW install stuff with pip or easy_install.</p> <pre><code>pip install flask </code></pre> <p>virtualenv basically sets your path to look in [venv folder]/bin for executables instead of /usr/local/bin or whatever. So you can copy files straight into your virtual env bin folder. (MongoDB files for instance just come in a zip/tar file, you can just untar them into your venv bin folder and you will have access to that particular version of MongoDB when 'sourced' in.) Try for yourself, run this command from your virtual and then default environment to see how it changes.</p> <pre><code>echo $PATH &amp;&amp; echo $PYTHONPATH </code></pre> <p>To exit out of your virtualenv:</p> <pre><code>deactivate </code></pre> <p>Typing this will get you back to your default environment.</p> <p>If you haven't read this yet, it's a pretty good resource.</p> <p><a href="https://python-guide.readthedocs.org/en/latest/dev/virtualenvs/">https://python-guide.readthedocs.org/en/latest/dev/virtualenvs/</a></p>
 

Querying!

 
Guidance

SQuiL has stopped working due to an internal error.

If you are curious you may find further information in the browser console, which is accessible through the devtools (F12).

Reload