title: Python3 Virtual Environment and PIP
body: <p>I'd like to play around in a virtual environment that's being interpreted purely via python3.3. On my system (Ubuntu 13.04), there are two ways to create a virtual environment. </p>
  
  <pre><code>virtualenv env
  </code></pre>
  
  <p>or: </p>
  
  <pre><code>pyvenv-3.3 env
  </code></pre>
  
  <p>If I use the old faithful, <code>virtualenv</code>, I'm able to use everything as expected, however, PIP installs everything into python2.7 libs rather than python3.3 libs. So, calling scripts using </p>
  
  <pre><code>python3 script.py 
  </code></pre>
  
  <p>Doesn't seem to work, yet: </p>
  
  <pre><code>python script.py 
  </code></pre>
  
  <p>Works like a charm. But, obviously must be using python2.7</p>
  
  <hr>
  
  <p>Now, if instead, I use the "built-in" venv from Python3+ (<code>pyvenv-3.3</code>), it seems that everything get's a little whacky. It correctly places a python3.3 lib folder in the venv, however, installing modules using PIP is no longer possible as it seems to somehow reference the global rather than the virtual environment. </p>
  
  <p>So, on to my question:</p>
  
  <p>How would you recommend getting a working virtual environment with ONLY Python3.3(+) and PIP installing to python3.3 libs? </p>