In previous versions, a shebang line like #! C:\full\path\to\executable or #! C:\venv\Scripts\python worked to specify the executable used to run the script. With the 3.11 py.exe launcher, this pattern is not recognized and uses a default Python interpreter instead.
I initially reported this in the comments of issue #94399 which was resolved several months ago.
Khold6458 commentedOct 26, 2022
•
edited by bedevere-bot
Bug report
In previous versions, a shebang line like
#! C:\full\path\to\executable
or#! C:\venv\Scripts\python
worked to specify the executable used to run the script. With the 3.11 py.exe launcher, this pattern is not recognized and uses a default Python interpreter instead.I initially reported this in the comments of issue #94399 which was resolved several months ago.
Your environment
The text was updated successfully, but these errors were encountered: