Ned Deily <nad@python.org> added the comment: Unfortunately, it may depend on what environment and/or from which distributor you obtain Python 3.6 as to whether there is a "python3" link installed. On Unix-like systems, the default Python installation built from source ("make install") does install both "python3.6" and "python3" links in the configured "bin" directory. But that may not be true everywhere. On what environment are you running Python 3.6 and from where was it installed? ---------- nosy: +ned.deily _______________________________________ Python tracker <report@bugs.python.org> <https://bugs.python.org/issue32553> _______________________________________

Change by Ned Deily <nad@python.org>: ---------- components: +Windows nosy: +paul.moore, steve.dower, tim.golden, zach.ware _______________________________________ Python tracker <report@bugs.python.org> <https://bugs.python.org/issue32553> _______________________________________

Paul Moore <p.f.moore@gmail.com> added the comment: Actually, for Windows, the docs don't recommend "python3", they say: """ On Windows, invoke the venv command as follows: c:\>c:\Python35\python -m venv c:\path\to\myenv """ This should probably be altered to say "py -m venv" (or maybe "py -3 -m venv", but I don't think that's really necessary), as using the launcher is less tied to having your PATH set, or using an explicit path. ---------- _______________________________________ Python tracker <report@bugs.python.org> <https://bugs.python.org/issue32553> _______________________________________

Paul Moore <p.f.moore@gmail.com> added the comment: That's why I suggest using the launcher rather than absolute paths - there are far too many variations to enumerate with absolue paths (you didn't mention per-user Python 3.6 installations, for example). If you have a suggested wording that you feel would explain things better, feel free to propose it. What's there at the moment seems relatively OK to me (aside from a minor tweak to use the launcher) so I'm not sure I could modify it in a way that would address your concerns. ---------- _______________________________________ Python tracker <report@bugs.python.org> <https://bugs.python.org/issue32553> _______________________________________

Paul Moore <p.f.moore@gmail.com> added the comment: Agreed, the docs don't need to mention PATHEXT. I don't have a machine to hand with Python 3.6 not installed, to check, but I believe the launcher is installed by default (although as you say it can be deselected - and it's definitely described as "recommended") whereas adding Python to PATH is deselected by default. So "py" is more likely to work on a typical installation than "python". As I say, though, I have no feel here for the right level of detail. Maybe something like """ To execute the venv command, use python -m venv Unix installations typically name the Python 3.x executable "python3", and on Windows the "py" launcher is generally available even if the Python interpreter is not on your PATH, so you may need to substitute the appropriate means of invoking Python in place of the "python" command above. """ But that's (to my mind) still wordy and complex - and the new users I've spoken to already find the docs too full of confusing detail. Ideally, I'd prefer it if "Invoking Python" were described once and for all in a separate section of the docs (i.e., the "Python Setup and Usage" manual) and everywhere else in the official documentation we simply used "python", with no qualifications, on the understanding that this stands for "whatever you use on your PC to run Python". I suspect that would generate complaints from a lot of people, though, as most people hit the doc pages via direct links, not by reading the manuals in order... ---------- _______________________________________ Python tracker <report@bugs.python.org> <https://bugs.python.org/issue32553> _______________________________________

Change by Eryk Sun <eryksun@gmail.com>: ---------- title: venv says to use python3 which does not exist in 3.6.4 -> Use the py launcher in venv Windows examples versions: +Python 3.10, Python 3.8, Python 3.9 -Python 3.6 _______________________________________ Python tracker <report@bugs.python.org> <https://bugs.python.org/issue32553> _______________________________________