title: Installing packages within canopy venv
body: <p>I am looking into using <a href="https://support.enthought.com/entries/23646538-Make-Canopy-s-Python-be-your-default-Python-i-e-on-the-PATH-" rel="nofollow">Canopy Express</a> as an IDE. My understanding is that it uses a backport of <code>venv</code> from Python 3 to <a href="https://support.enthought.com/entries/21802240-Use-venv-not-virtualenv-with-Canopy-Python" rel="nofollow">manage user-generated virtual environments</a>, in addition to being <a href="http://docs.enthought.com/canopy/configure/faq.html#where-are-all-of-the-python-packages-in-my-user-python-environment" rel="nofollow">a virtual environment unto itself</a>. I just want to verify that within any virtual environments I create in Canopy, I will be able to install project-specific packages not included in the Express distribution using <code>easy_install</code>/<code>pip</code> as described <a href="https://support.enthought.com/entries/23389761-Installing-packages-into-Canopy-Python-from-the-command-line" rel="nofollow">here</a>. That last link doesn't explicitly say that such package management works in a user-created virtual environment, hence my uncertainty.</p>
  
  <p>Put simply, what I want is (assuming all my projects are 2.7-based) to install Canopy Express once and use it as my default Python. Then for various projects requiring packages that Express doesn't include, I can create separate virtual environments and install such packages on an as-needed basis.</p>
  
  <p>If I can't do this, the other alternative I see is to install Canopy Express in <code>virtualenv</code> environments on an as-needed basis, and then to use those environment's <code>pip</code>s to install extra packages.</p>
  
  <p>Any thoughts?</p>