Jens Lindgren added the comment:
I just got hit by this bug and would like to add my thoughts on this.
If you are in an activated venv, no matter if you launch with command python or
python3, it will launch the version in venv (version 3.6.1 in this case).
I expect the py-launcher and shebang
Jens Lindgren added the comment:
Sorry I need to clarify.
On Linux both python and python3 works as there is a symlink created from
python to python3 in the venv folder.
On Windows only python.exe is created. I copied it to python3.exe. Now I can
use python3 script.py to start but py-launcher