title: Using mkproject in Python's virtualenv
body: <p>I'm trying to understand when is best to use <code>mkproject</code> vs <code>mkvirtualenv</code> when using <code>virtualenvwrapper</code>.</p>
  
  <p>I found a couple of answers of what is the difference between the two <a href="https://stackoverflow.com/questions/9811942/differentiate-mkvirtualenv-and-mkproject-for-virturalenvwrapper">here</a> and <a href="https://stackoverflow.com/questions/8288297/whats-the-relationship-between-environments-and-projects-in-virtualenvwrapper/9425560">here</a>.</p>
  
  <p>From the second link, this seems to be the best summary of the differences:</p>
  
  <blockquote>
    <p>From my understanding of the documentation, <code>mkvirtualenv projectenv</code> simply creates a new virtual environment named <code>projectenv</code> in <code>$WORKON_HOME</code>, while <code>mkproject projectenv</code> creates a new virtual environment named <code>projectenv</code> and a new directory named <code>projectenv</code>; after creation, the <code>projectenv</code> directory automatically becomes your current working directory. The virtual environment will exist in <code>$WORKON_HOME</code> and the development directory exists in <code>$PROJECT_HOME</code>.</p>
  </blockquote>
  
  <p>When would it be more appropriate to use <code>mkproject</code> and when <code>mkvirtualenv</code>? I would really find an example of the differences useful if possible.</p>