PyCharm virtualenv support

In case it helps, this:

virtualenv is now supported (to configure, go to Settings | Python Interpreter, click Add, and select the python script inside the Scripts subdirectory of your virtualenv directory);

refers to the file ~/.virtualenv/project/bin/python
You can add the interpreter in global settings, but leave the main interpreter selected, and then go into Run | Edit Configurations to specify the specific interpreter for your project.
-Ed
6 comments
Comment actions Permalink

But it happen to me that this way changed the interpreter for all my prjects... not only the one I changed

0
Comment actions Permalink

Hello Esteban,

Which way? The list of available Python interpreters is shared between all

projects, but the specific intepreter selected in Settings | Python Interpreters

is stored per project.

But it happen to me that this way changed the interpreter for all my

prjects... not only the one I changed

--

Dmitry Jemerov

Development Lead

JetBrains, Inc.

http://www.jetbrains.com/

"Develop with Pleasure!"

0
Comment actions Permalink

Yes you are Right.... I missed that I can select it.

Thanks

0
Comment actions Permalink

The problem with this is, PyCharm seems to parse and load into memory every interpreter from every project at all times.

If I have, say, 7 different virtualenvs set up and imported in PyCharm, the IDE runs MUCH slower than if I delete 5 of them.

Quite annoying. There's no reason, if I have project A open which uses virtualenv A1, that it should go and parse and stick into memory information about virtualenv A2.

0
Comment actions Permalink

Hello Daniel,

PyCharm keeps only a minimal amount of information about each virtualenv

in memory; it certainly does not parse all of the classes or keep all of

the information on them in memory.

If you can reproduce the performance problems with many virtualenvs configured,

please capture a CPU snapshot as described in http://devnet.jetbrains.net/docs/DOC-1212

and file a YouTrack issue with the snapshot attached.

The problem with this is, PyCharm seems to parse and load into memory

every interpreter from every project at all times.

If I have, say, 7 different virtualenvs set up and imported in

PyCharm, the IDE runs MUCH slower than if I delete 5 of them.

Quite annoying. There's no reason, if I have project A open which uses

virtualenv A1, that it should go and parse and stick into memory

information about virtualenv A2.

--

Dmitry Jemerov

Development Lead

JetBrains, Inc.

http://www.jetbrains.com/

"Develop with Pleasure!"

0
Comment actions Permalink

I will certainly try to get around to doing this.

With many virtualenv paths set up in PyCharm, on my work laptop, it runs exceedingly choppy and slow. When I disable them it's noticeably faster... I'll try to catch it in the act and post the CPU results.

Thanks

0

Please sign in to leave a comment.