Description
Coming from pypa/pip#5526
On Windows, the python.org installers do not add a pythonX.Y.exe
file. So, unless the user goes out of their way, it's basically guaranteed that pythonX.Y
isn't something on PATH. Thus, on Windows, tox should try to use the py
launcher for Windows to run interpreters if it does not find existing pythonX.Y
interpreters on PATH. Essentially, pythonX.Y
on Unix is equivalent on Windows would be py -X.Y
with the advantage of being user configurable.
This would allow tox to operate out-of-the-box on Windows a lot more cases than today, mostly as long as some Python 3.3+ interpreter is installed (there's some cases where py doesn't get added to PATH).
This could essentially take form of tox doing extra work on Windows if pythonX.Y
is not on PATH -- the extra work to also try to use py -X.Y
.