title: differentiate mkvirtualenv and mkproject for virturalenvwrapper
body: <p>I am talking about <a href="http://www.doughellmann.com/docs/virtualenvwrapper/" rel="nofollow">Doug Hellman's virtualenvwrapper</a>. Well, as per him, once we install virtualenvwrapper, we should edit the .bashrc file as explained <a href="http://www.doughellmann.com/docs/virtualenvwrapper/install.html#shell-startup-file" rel="nofollow">here</a></p>
  
  <p>what we do is we add the following three lines of code:</p>
  
  <pre><code>export WORKON_HOME=$HOME/.virtualenvs
  export PROJECT_HOME=$HOME/Devel
  source /usr/local/bin/virtualenvwrapper.sh
  </code></pre>
  
  <p>where .virtualenv is the directory where the venvs would be placed. 
  Devel is the directory where the code will reside. </p>
  
  <p><strong>Observation 1:</strong>
  when i do <code>mkvirtualenv proj1</code> what happens is a directory called proj1 is created inside .virtualenv but NOT inside Devel. </p>
  
  <p><strong>Observation 2:</strong>
  When i do <code>mkproject proj1</code>, a directory inside .virtualenv as well as inside Devel is created. </p>
  
  <p>Now the questions:</p>
  
  <ol>
  <li><p>Please explain <em>observation 1</em>. </p></li>
  <li><p>What if two project have same requirements and i want to use a single env and would not want to start with creating another virtualenv and re install the same thing that is installed. How do i do this?</p></li>
  </ol>