Bajron

You can do something like that (assuming cmd.exe) ``` dotenv run %VIRTUAL_ENV%\Scripts\python -c "import sys; print(sys.executable)" ``` Current behavior is just Python behavior. Compare ``` python -c "import sys; print(sys.executable)"...

I tried to reproduce this, but with no luck. Could you confirm the example from https://gist.github.com/Bajron/da5ce70430c0e071bc1b68161a311d6b is enough to replicate the problem in your environments? This is mostly the example...

I am on Windows 10 22H2, tried in `cmd`, `powershell`, wsl Ubuntu, wsl Debian. Cannot get the problem. Used python 3.11.1, now updated to 3.11.7, still nothing. If you can...

Note the `dotenv_values()` output is ok in this case, so reading file and parsing seems fine. (perhaps you could use it as a workaround in your application for now) It...

I am afk for some time, could you try the same without the single quotes in cmd. Is it the same for test_env.py?

@bill-ash could check setting the value directly to os.environ and reading it back? I mean the one that stopped working for you after some time. So far it seems like...

Took a look at this one. I think we can change the assertion into breaking the loop. I checked the history and it seems the assertion is there to make...

Added a PR with my suggestion. I think we still need to understand what actually happens in your environment though. You can test it with: `pip install python-dotenv@git+https://github.com/Bajron/python-dotenv@assertion-find-dotenv-for-upstream` You might...