Using an existing virtualenv directory Follow
Hi, I'm looking at the new virtualenv GUI in PyCharm v2.5. Is there a way to point it to an existing virtualenv setup?
I've been using virtualenv by adding the python interpreter inside the virtualenv directory into the IDE's interpreters list. My project still runs OK in pycharm v2.5, but it gives me a validation error that it can't find a PIP package requirement. Oddly, pycharm can find the 'missing' lib just fine in the Packages pane of the Python Interpreters setting window.
Also, what are the benefits of using the virtualenv GUI rather than just overriding the interpreter path?
Please sign in to leave a comment.
The new virtualenv GUI is a UI for creating new virtual environments. If you have an existing virtual environment, you need to add it as an interpreter, just as you did in previous PyCharm versions.
As for the incorrect 'missing pip' diagnostics, which version of Python and virtualenv are you using?
The package it can't find is Flask 0.8.0. The PKG-INFO for Flask says '0.8'. It seems they're a little inconsistent about whether there's two digits or three. Command line virtualenv didn't seem to mind either way. I think the error goes away if I edit my requirements.txt to specify 0.8, but I'm not sure that I'm rerunning the right inspection in PyCharm.
I've filed a YouTrack issue: http://youtrack.jetbrains.com/issue/PY-6355