Tzu-ping Chung <uranu...@gmail.com> added the comment: >> not enough since it’d break `flit install --python=py` because that’s give >> you the location of py.exe, not the actual interperter. > This would be fine if you still run the process to get its sys.executable.
But then I need two separate workflows based on what is passed in. For py.exe I need to run it and get sys.executable. But for python.exe I *cannot* use sys.executable because that’s the base interepeter, not the venv path I want. And `if Path(arg).stem == "py"` just seems like a bug waiting to happen. > Your specific example would never have worked, FWIW, as it always would have > picked up pythonA rather than the application one or the base one, unless you > were relying on python3/python3.7 not being available on Windows (which is no > longer true - they are included in the Store package now). It is an illustration. I am fully aware of Windows not having version-named python executables. Thanks for the reminder anyway. ---------- _______________________________________ Python tracker <rep...@bugs.python.org> <https://bugs.python.org/issue38905> _______________________________________ _______________________________________________ Python-bugs-list mailing list Unsubscribe: https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
