PYTHONPATH gets overwritten when running tests

[karthiknadig]

Hello, I am facing the same issue. On one computer it works, on another it doesn't. Both run VS Code insiders, updated daily. Both have exact same .vscode/settings.json.

one loads the .env variables correctly in integrated python (python test runnter), the other doesn't.

Any hints for debugging this?

EDIT: also installing python-dotenv does not alleviate this. I can confirm that python-dotenv works (when running pytest from commandline), but when I run the tests using the sidebar, it seems like VS Code is overwriting all env variables with some internal state, hence also resetting PYTHONPATH to "."

Originally posted by @niderhoff in #6891 (comment)

[karthiknadig]

@niderhoff Created this new issue to track the problem.

[niderhoff]

Hi, thanks for doing that. As mentioned in the initial comment, I have both systems ready (one where it is working, one where it is not) so let me know which commands I can run to extract some information from both System in order to debug the issue.

[karrtikr]

Can you provide contents of .env file in your workspace? Try debugging a Python file which prints out PYTHONPATH variable on both systems.

We investigate issues in order based on priority and severity, which includes the impact it has on your ability to use the extension to do productive work, and the number of people affected. If other users come forward and leave a comment demonstrating they are seeing/reproducing the problem then we will raise this issue's priority. Thanks for understanding and the patience!

[karrtikr]

@karthiknadig This doesn't seem to be related to environments but testing itself, so re-assigning.

[dschultz5197]

I'm having the same issue where testing is not working within the environment I'm in. In the terminal I can run the pytest command and everything works properly, however the test runner does not seem to accept the environment variables (notably PYTHONPATH) and thus can not find the custom modules I'm trying to test.

[brettcannon]

Because we have not heard back with the information we requested, we are closing this issue for now. If you are able to provide the info later on, then we will be happy to re-open this issue to pick up where we left off.