title: How do I clear a stale pypi package from Heroku/Cedar's virtualenv?
body: <p>I am building my own <code>flask-oauth</code> in my app's src/lib and adding it to the web application's path via: <code>sys.path.insert(0, os.getcwd() + '/src/lib/flask-oauth')</code>  I have to do this because the pypi package doesn't have support for access_token_params, which google requires.</p>
  
  <p><code>flask-oauth</code> does not appear in <code>requirements.txt</code> currently, but it did in the past. As a result, it remains in my heroku app's vitualenv and I cannot get rid of it. My app works locally, but on heroku it dies with: </p>
  
  <pre><code>TypeError: __init__() got an unexpected keyword argument 'access_token_params'
  </code></pre>
  
  <p>I have tried listing the latest github version of flask-oauth in my <code>requirements.txt</code> file as in: <code>git+git://github.com/mitsuhiko/flask-oauth.git</code>, and the package does install. However, the application still loads the stale version from <code>/app/.heroku/venv/lib/python2.7/site-packages/flaskext/oauth.py</code> and the app still dies.</p>
  
  <p>I have this in my requirements.txt:</p>
  
  <pre><code>-e git://github.com/mitsuhiko/flask-oauth.git@80167c44abc3df37e43a45474d19452065430464#egg=Flask_OAuth-dev
  </code></pre>
  
  <p>And the correct, latest, github version of flask-oauth now installs locally and works. But I still can't get heroku to acknowledge or use that package in the app. It uses their old version in <code>/app/.heroku/venv/lib/python2.7/site-packages/flaskext/oauth.py</code></p>
  
  <p>How can I clear heroku's virtualenv of this stale package? How can I make it use the github version and not its cached package?</p>
  
  <p>Note: I have created a new app called mythin-dev, and it reads my requirements.txt and installs the correct version of flask-oauth from</p>
  
  <pre><code>-e git://github.com/mitsuhiko/flask-oauth.git@80167c44abc3df37e43a45474d19452065430464#egg=Flask_OAuth
  </code></pre>
  
  <p>So it seems that the problem is definitely the cached packages in my heroku virtualenv. Help, my application will not run on heroku until this is resolved :(</p>