wdhwg001 added the comment:
Okay. But somehow I still think the current way of handling shebang is
confusing. That makes a python3-only script unable to find a way to use both
versioned shebang and virtualenv.
Maybe it could be changed to `Command is eligible for path search, or there is
no
wdhwg001 added the comment:
And during the entire testing procedure, `C:\Users\wdhwg001\study\venv\Scripts`
was manually added to user `PATH` and system `PATH`, but `py.exe` cannot find
the hardlinked `python3.exe` in there.
--
___
Python tracker
wdhwg001 added the comment:
But actually after I created a `python3.bat` into venv/Scripts, the shebang `#!
/usr/bin/env python3` still does not take the `python3.bat`.
Then I created a hardlink from `python.exe` to `python3.exe`, the shebang still
does not work.
I didn't check the co
New submission from wdhwg001:
https://github.com/pypa/virtualenv/issues/979
TL;DR
py.exe does not search PATH when using `#! /usr/bin/env python3`.
And the right steps I think should be:
1. Search ./
2. Search PATH
3. Fallback to system installed Python 3
But currently py.exe seems only do
