[BUG] dotenv cli not used windows venv if it activated #373

Activity

1. Niccolum commented on Jan 27, 2022

   

   Niccolum

   on Jan 27, 2022

   Last edited by Niccolum

   Author

   More actions

   Found interesting issue in CPython about it
   https://bugs.python.org/issue38905

   Have you any ideas how to solve this?

   I have idea with one crutch:

   command = [
       sys.executable if s == "python" and os.name == "nt" else s 
       for s in command
   ]
   

   Somewhere before https://github.com/theskumar/python-dotenv/blob/master/src/dotenv/cli.py#L153

   But I didn't test this yet

   Also we can add check sys.version_info in this crutch, but i haven't all supported python version on windows. I see you have tox, so we can come up with test for that and add different OS in tox (platform parameter) for check it for that, if you support this change.
2. Niccolum

   changed the title [-][Question] dotenv cli not used windows venv if it activate?[/-] [+][BUG] dotenv cli not used windows venv if it activated[/+] on Jan 28, 2022
3. Niccolum commented on Jan 29, 2022

   

   Niccolum

   on Jan 29, 2022

   Author

   More actions

   UPD: crutch is working!

   👍React with 👍2Reacted by Ihar and Miles Zhang
4. Indiana3714 commented on Sep 1, 2022

   

   Indiana3714

   on Sep 1, 2022

   More actions

   Any chance the fix above can be merged? (assuming it works)

   👍React with 👍1Reacted by Eliise
5. EliiseS commented on Mar 14, 2024

   

   EliiseS

   on Mar 14, 2024

   More actions

   Any fix for this? Still running into this issue in windows

   👍React with 👍1Reacted by MahrRah
6. MahrRah commented on Mar 14, 2024

   

   MahrRah

   on Mar 14, 2024

   More actions

   Same issue here.

   👍React with 👍1Reacted by Eliise
7. Bajron commented on Mar 15, 2024

   

   Bajron

   on Mar 15, 2024

   More actions

   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)"
   

   and

   python -c "import subprocess; subprocess.run(['python','-c', 'import sys; print(sys.executable)'])"
   

   Also, see the warning in Popen documentation https://docs.python.org/3/library/subprocess.html#subprocess.Popen

   Following the suggestions in the warning I created a pull request #508 . I believe resolving against the PATH is what most of the users expect.
   You can try it with:

   pip install python-dotenv@git+https://github.com/Bajron/python-dotenv@dotenv-run-resolve-path-for-upstream[cli]
   

   Most likely you need to uninstall the old version first as the version string is still the same and pip might not apply the changes because of that.

   👍React with 👍1Reacted by MrSnapperVibes