[issue34359] Wrong virtual environment found

Change by sfx2k : -- stage: -> resolved status: open -> closed ___ Python tracker ___ ___ Python-bugs-list mailing list Unsubscribe

[issue34359] Wrong virtual environment found

Stéphane Wirtel added the comment: it's normal because this path is in the PATH env variable. so in this case, I think we can close this issue. -- ___ Python tracker ___ _

[issue34359] Wrong virtual environment found

sfx2k added the comment: Okay, thanks anyway :) btw: "Oh, and I suspect that the reason that "The thing with the relative path works if I change the order in the path" is simply because the bit of code that searches PATH just ignores what's after #!/usr/bin/env and looks for python.exe. (M

[issue34359] Wrong virtual environment found

Stéphane Wirtel added the comment: Now, you could use a Windows shortcut where you specify the version of Python when you execute your script. F:\python\scripts3\.venv\bin\python myscript.py For example. -- nosy: +matrixise resolution: not a bug -> stage: resolved -> status: closed

[issue34359] Wrong virtual environment found

Paul Moore added the comment: Oh, and I suspect that the reason that "The thing with the relative path works if I change the order in the path" is simply because the bit of code that searches PATH just ignores what's after #!/usr/bin/env and looks for python.exe. (More or less - I haven't ch

[issue34359] Wrong virtual environment found

Paul Moore added the comment: Others use absolute paths, as I mentioned in my reply. -- ___ Python tracker ___ ___ Python-bugs-list

[issue34359] Wrong virtual environment found

Change by Paul Moore : -- resolution: -> not a bug stage: -> resolved status: open -> closed ___ Python tracker ___ ___ Python-bug

[issue34359] Wrong virtual environment found

sfx2k added the comment: Thanks for your feedback, Paul and Stephane. The thing with the relative path works if I change the order in the path from [...]F:\Python\scripts3;F:\Python\projects\timetracking[...] to [...]F:\Python\projects\timetracking;F:\Python\scripts3[...] ;) An absolut pa

[issue34359] Wrong virtual environment found

Stéphane Wirtel added the comment: And the Shebang is specific to the Unix-like systems, the loader from the operating system, will read the first line and will try to execute the defined interpreter. https://en.wikipedia.org/wiki/Shebang_(Unix) On Windows, I am not sure, but like Paul told

[issue34359] Wrong virtual environment found

Paul Moore added the comment: >From https://docs.python.org/3.7/using/windows.html#shebang-lines the >supported shebang lines are * /usr/bin/env python * /usr/bin/python * /usr/local/bin/python * python There's a provision in there: """ The /usr/bin/env form of shebang line has one further

[issue34359] Wrong virtual environment found

New submission from Sascha Fuhrmann : For my python development I have several directories on my Windows system: common: F:\python\scripts -> one-file-scripts based on python 2 F:\python\scripts3 -> one-file-scripts base on python 3 projects: F:\python\projects\timetracking ... Each directory