Pytest doesn't add PYTHONPATH itself

[myusko]

Hello, and thank you for the cool tool! but I noticed that, when I tried to run tests via pytest command.

I'm always got the E ModuleNotFoundError: in order to fix the issue, we need to run python -m pytest manually, or just export PYTHONPATH to root directory.

Will be cool, if Pytest will do it itself, thank you;)

[pytestbot]

GitMate.io thinks possibly related issues are #532 (pytest -f does not notice new tests), #2196 (Pytest on cygwin doesn't find files), #1026 (pytest.warn doesn't appear to be working for deprecation warnings), #3312 (pytest.approx doesn't support comparison between arrays and scalars), and #1037 (pytest.deprecated_call doesn't catch PendingDeprecationWarnings).

[RonnyPfannschmidt]

this is expected and planned behaviour, actually it came to attention that module execution is a problematic way to run things

if we always add the worktree we completely ruin sanely testing packages that where installed with tests from the worktree

[myusko]

@RonnyPfannschmidt Got it, thank you for the clear explanation

[nicoddemus]

Closing this for now then. 👍