How and why does PyCharm alter Python's import logic?

python import pythonpath pycharm
Roman picture Roman · Apr 26, 2011 · Viewed 9.7k times · Source

I have a PyCharm 1.2.1 on Windows. I have to edit different branches of the same project - somewhat heavy branches, because they live in different folders on disk - say it to be c:\apps\alpha and c:\apps\beta. For each such folder PYTHONPATH variable should be adjusted to point to appropriate vendor libraries which live somewhere inside project root folder (c:\alpha\vendor,...). I managed to work around this issue by starting PyCharm from cmd batch file which sets necessary PYTHONPATH variable value before starting PyCharm (so I have PyCharm.cmd inside alpha and PyCharm.cmd inside beta directories).

Problem: when I open PyCharm for editing beta folder, import statement imports modules from alpha folder! When I start python.exe interpreter from command line everything works as expected - the problem seems to be only with PyCharm.

Second strange investigation: executing print sys.path code from PyCharm and from external python.exe interpreter give different results - from PyCharm it do not show my PYTHONPATH modules. I'm a newcomer in Python and PyCharm, but this behavior looks very strange and inconsistent.

Finally I've found some settings in PyCharm IDE that looks like should allow me to resolve this issue - File -> Settings -> Python Interpreter. There I've found all paths for both alpha and beta folders. There is no way to clear this paths list, only to disable some elements. But even disabling works somewhat stupidly - I should disable/re-enable them separately for each time I edit alpha or beta "solution folders".

So final question: how one can with PyCharm edit separate projects (folders) and force PyCharm not to import modules from wrong locations?

Answer

yole picture yole · Apr 26, 2011

The correct solution is not to try to work around PyCharm's logic, but rather to use the IDE features as they're designed. That means:

  • Not use any .cmd scripts for starting up PyCharm
  • Remove all the paths specific to "alpha" and "beta" from the list of paths in Settings | Python Interpreters if any are listed there
  • Mark the "alpha/vendor" and "beta/vendor" directories as source roots in the alpha and beta projects respectively.

Then PyCharm will resolve imports correctly and generate the correct PYTHONPATH automatically when running the application from it.

Related questions

How do I import a Python script from a sibling directory?

Here is the directory structure: parent_dir/ foo_dir/ foo.py bar_dir/ bar.py How do I import bar.py into foo.py?

Read More
Call a function from another file?

Set_up: I have a .py file for each function I need to use in a program. In this program, I need to call the function from the external files. I've tried: from file.py import function(a,b) But …

Read More
Import Error: No module named numpy

I have a very similar question to this question, but still one step behind. I have only one version of Python 3 installed on my Windows 7 (sorry) 64-bit system. I installed numpy following this link - as suggested in the question. …

Read More