Why does 'pytest tests/unit' work with docker but not locally?

[cosmicpython]

Why does 'pytest tests/unit' work with docker but not locally?

[hjwp]

hey frank! basically the project is designed so that you pip install the src directory, and then the allocation module becomes part of your virtualenv packages:

pip install -e src

I'm sorry i didn't document that in the Readme. I'll try and add that shortly. there is a brief mention of it in https://www.cosmicpython.com/book/appendix_project_structure.html tho

[frankbolero]

Ok. I'm gonna answer myself here. :)
First of all, I'm a bit new to Python so there's that, plus tooling. I had some hour or so earlier trying to solve this and couldn't so I wrote the above and then went to try and solve it even more (a k a having a better look at the pytest documentation). :)

Running tests locally can be done by making sure you are running python -m pytest ../tests/unit from the src-directory. Perhaps there are some other ways of solving this, if you want to run pytest manually the ´make unit-tests´ does that obviously.

The pyCharm issue was solved by making sure that pyCharm actually understood where the actual sources were kept.

As for pycrunch-tooling in pyCharm, there seems to be some version mismatch with Socket.IO or Engine.IO which I guess Flask uses.