0

I am pretty new to Python. Currently I am trying out PyCharm and I am encountering some weird behavior that I can't explain when I run tests.

The project I am currently working on is located in a folder called PythonPlayground. This folder contains some subdirectories. Every folder contains a init.py file. Some of the folders contain nosetest tests.

When I run the tests with the nosetest runner from the command line inside the project directory, I have to put "PythonPlayground" in front of all my local imports. E.g. when importing the module called "model" in the folder "ui" I have to import it like this:

from PythonPlayground.ui.model import *

But when I run the tests from inside Pycharm, I have to remove the leading "PythonPlayground" again, otherwise the tests don't work. Like this:

from ui.model import *

I am also trying out the mock framework, and for some reason this framework always needs the complete name of the module (including "PythonPlayground"). It doesn't matter whether I run the tests from command line or from inside PyCharm:

with patch('PythonPlayground.ui.models.User') as mock:

Could somebody explain the difference in behavior to me? And what is the correct behavior?

svb
  • 641
  • 1
  • 7
  • 13

1 Answers1

1

I think it happens because PyCharm have its own "copy" of interpreter which have its own version of sys paths where you project's root set to one level lower the PythonPlayground dir. And you could find preferences of interpreter in PyCharm fro your project and set proper top level. ps. I have same problems but in Eclipse + pydev

Denis
  • 7,127
  • 8
  • 37
  • 58
  • 2
    This seems correct, as suggested by [this](http://stackoverflow.com/questions/5794502/pycharm-and-pythonpath-issue-how-and-why-pycharm-alter-python-import-logic) answer. – Bakuriu Sep 04 '12 at 11:07
  • This was indeed correct. Moving my source files to a directory called "src", and marking this directory as a source directory in the project settings, solved the problem :) – svb Sep 05 '12 at 08:22