Why (or how) does calling pytest skip calling sitecustomize.py

[flexatone]

If python is started without the -S flag, it configures the site and calls sitecustomize.py if it exists in site-packages.

However, if I create a sitecustomize.py and run pytest from the command line, sitecustomize.py is not called.

On the other hand, if I call python -m pytest, sitecustomize.py is called.

I can see in the launcher script in the virtual env bin directory that it is using a #! to get at the same python executable, and I do not see the -S flag being used.

So how is it that pytest is not calling sitecustomize.py when evoking pytest from the command line?

[RonnyPfannschmidt]

The pytest binary doesn't mess around with adding cwd to the pythonpath

https://docs.pytest.org/en/stable/explanation/pythonpath.html#invoking-pytest-versus-python-m-pytest

[flexatone]

Thanks, @RonnyPfannschmidt , for your response. After further investigation it turns out that I was executing a pytest in a different virtual environment than which pytest told me, and where there was not a sitecustomize.py. I can confirm that, once I got to the right pytest, it does indeed call sitecustomize.py as expected.

Thanks for your help.