[issue32553] venv says to use python3 which does not exist in 3.6.4

Terry J. Reedy added the comment: As far as I know, Windows binaries have only been named python.exe or pythonw.exe. Before 3.5, I believe, "C:\Pythonxy", where x,y were major,minor, *was* the default Windows installation directory. 'Python35' must have been the result of

[issue32553] venv says to use python3 which does not exist in 3.6.4

Paul Moore 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

[issue32553] venv says to use python3 which does not exist in 3.6.4

Eryk Sun added the comment: `PATHEXT` is irrelevant here, so that should be removed. As to the py launcher, it's optional and not always installed for all users, though that's the default. I'd prefer `python` that's found in PATH as the first example. Then add another

[issue32553] venv says to use python3 which does not exist in 3.6.4

Paul Moore 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

[issue32553] venv says to use python3 which does not exist in 3.6.4

Paul Watson added the comment: Ok, I do find later on where it says to do something different on Windows. However, the first "Note" box in "28.3. venv" specifies using "python3". It does not say that this is for non-Windows systems. This should be changed. Also,

[issue32553] venv says to use python3 which does not exist in 3.6.4

Paul Moore 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

[issue32553] venv says to use python3 which does not exist in 3.6.4

Ned Deily added the comment: Thanks! Pinging the Windows team. -- ___ Python tracker ___

[issue32553] venv says to use python3 which does not exist in 3.6.4

Change by Ned Deily : -- components: +Windows nosy: +paul.moore, steve.dower, tim.golden, zach.ware ___ Python tracker ___

[issue32553] venv says to use python3 which does not exist in 3.6.4

Paul Watson added the comment: I am running 3.6.4 from a download on pythong.org yesterday. Python 3.6.4 (v3.6.4:d48eceb, Dec 19 2017, 06:54:40) [MSC v.1900 64 bit (AMD64)] on win32 There is a python3.dll, but no python3 executable. --

[issue32553] venv says to use python3 which does not exist in 3.6.4

Ned Deily 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

[issue32553] venv says to use python3 which does not exist in 3.6.4

Mariatta Wijaya added the comment: People who has more than one Python versions installed will have python3. -- nosy: +Mariatta ___ Python tracker

[issue32553] venv says to use python3 which does not exist in 3.6.4

New submission from Paul Watson : The 3.6.4 documentation on venv specifies using 'python3', but no python3 executable is in the 3.6.4 kit. https://docs.python.org/3/library/venv.html?highlight=venv#module-venv -- assignee: docs@python components: