title: Python3 pip installing globally when in a virtualenv
body: <p>Attempting to finally make the jump to Python 3, but am running into some issues with virtualenvwrapper. I start out by creating the virtual environment like so:</p>
  
  <p><code>mkvirtualenv -p /usr/local/bin/python3 projectname</code></p>
  
  <p>which yields:</p>
  
  <pre><code>Running virtualenv with interpreter /usr/local/bin/python3
  Using base prefix '/usr/local/Cellar/python3/3.3.3/Frameworks/Python.framework/Versions/3.3'
  New python executable in projectname/bin/python3.3
  Also creating executable in projectname/bin/python
  Installing setuptools, pip...done.
  </code></pre>
  
  <p>So far, so good. I check the python console to make sure that the environment is looking at the correct interpreter and all that and it is. Here's where sadness happens (while the virtualenv is active):</p>
  
  <p><code>pip install flask</code> claims to be successful, but alas:</p>
  
  <pre><code>Python 3.3.3 (default, Jan  2 2014, 13:26:32) 
  [GCC 4.2.1 Compatible Apple LLVM 5.0 (clang-500.2.79)] on darwin
  Type "help", "copyright", "credits" or "license" for more information.
  &gt;&gt;&gt; import flask
  Traceback (most recent call last):
    File "&lt;stdin&gt;", line 1, in &lt;module&gt;
  ImportError: No module named 'flask'
  </code></pre>
  
  <p>Here's the issue:</p>
  
  <pre><code>$ pip show flask
  ---
  Name: Flask
  Version: 0.10.1
  Location: /usr/local/lib/python3.3/site-packages
  Requires: Werkzeug, Jinja2, itsdangerous
  </code></pre>
  
  <p>Unless I'm completely misunderstanding virtualenv/wrapper and their respective magics (which I very well could be), it seems like pip install is installing Flask globally rather than to the site-packages within my virtualenv, and thus the virtualenv is ignoring it.</p>
  
  <p>Any clues what's going on here/how to fix? Am I wrong in assuming that virtualenvwrapper is ready for primetime with python3? Pretty solutions where I don't have to mangle my .bashrc or manually set environment variables are preferable. I'm hoping there's a way to do this through the api's provided by virtualenv and virtualenvwrapper.</p>
  
  <p>Thanks!</p>