PYTHONPATH for unittest_discovery.py

[benbuckman]

Hi,
I'm using:

• VSCode v1.76.2
• Python extension v2023.4.1
• Python 3.10.6

Our application requires multiple paths set in PYTHONPATH to appease the assumptions of various frameworks.

I'm having trouble getting this to work with the Tests panel and its unittest_discovery.py script.

I've tried setting PYTHONPATH with an .env file and with terminal.integrated.env.osx.PYTHONPATH in settings.json.
If I hack sys.stderr.write(f"{__file__} PYTHONPATH is: {os.environ.get('PYTHONPATH')}\n") into unittest_discovery.py, it prints out PYTHONPATH is: None.

Consequently, it's not finding all my tests, and it's showing ModuleNotFound errors.

I see that a similar issue was raised in #17179 and concluded as not having sufficient backing. Is that the end of it?
I also see an earlier #17363 where it seems like a similar issue was fixed. So that's confusing.

What is the correct way to set PYTHONPATH for test discovery in the Testing panel? Or is there no way currently?

Thank you!

[brettcannon]

Until we improve our .env file support, the best way is going to be launching VS Code from a terminal that has PYTHONPATH set. Then all of VS Code will inherit the environment variable and it should just flow down into pytest itself.