Repository navigation
Usage of venv specifies a python3 command not found in 3.11.2 on Windows #102354
Description
Activity
A few lines later there are specific instructions for Windows:
On Windows, invoke the venv command as follows:
c:\>c:\Python35\python -m venv c:\path\to\myenvAlternatively, if you configured the PATH and PATHEXT variables for your [Python installation] (https://docs.python.org/3/using/windows.html#using-on-windows):
c:\>python -m venv c:\path\to\myenvGrepping the entire
Doc/directory, I see 156 occurrences ofpython -mand only 8 ofpython3 -m, so it seems likepython -mis much more common in our documentation, despite the fact that amake installof Python 3 on most platforms doesn't install apythonbinary at all. So I'm not clear what the docs should prefer or standardize on here.python -m ...does not work on all platforms, unless you are in a venv, or your distro or someone else has decided to linkpythontopython3. Just building and installing python on POSIX installs onlybin/python3, there's nopython.I feel sure this is something that has been discussed before; I'll see if I can find out what the thinking has been.
Looks like the conclusion in #98761 was that
python -m ...should be preferred in the docs. So @Liturgist, if you are interested in making a pull request to convert the few cases ofpython3 -m ...topython -m ...(including this one), it looks like that would be appropriate.See also #102358 for providing
bin/pythoninmake install, so we are more consistent in our preference forpython -m ....- changed the title
[-]Usage of venv specifies a python3 command not found in 3.11.2[/-][+]Usage of venv specifies a python3 command not found in 3.11.2 on Windows[/+]on Mar 1, 2023 @carljm, here are the mentions of
python 3 -mI find. It would appear that this specific issue is about./using/venv-create.inc. Is that the only change to be made? Should others be considered. Is this issue, #102354, the one to fix?PS C:\src\cpython\Doc> dir -File -Recurse * | %{sls 'python3 -m' $_} Makefile:157: $(VENVDIR)/bin/python3 -m pip install -U pip setuptools; \ Makefile:158: $(VENVDIR)/bin/python3 -m pip install -r requirements.txt; \ library\__main__.rst:262: block. You can invoke it with ``python3 -m venv [directory]``. library\importlib.metadata.rst:76: $ python3 -m venv example library\pdb.rst:61: python3 -m pdb myscript.py library\pdb.rst:75: ``python3 -m`` does. As with a script, the debugger will pause execution just tutorial\venv.rst:47: python3 -m venv tutorial-env using\venv-create.inc:4: python3 -m venv /path/to/new/virtual/environment whatsnew\3.10.rst:1542: The ``python3 -m module-name`` command startup time is 1.4x faster in whatsnew\3.6.rst:2060:The ``pyvenv`` script has been deprecated in favour of ``python3 -m venv``.I think it makes sense to be consistent in our usage in the docs, so I think it would be fine to update all of the cases (other than the Makefile.) And yes, you can use this issue.
- added a commit that references this issue
on Mar 14, 2023
Documentation
The documentation on using
venvat https://docs.python.org/3/library/venv.html for 3.11.2 specifies to use apython3executable.I do not find a
python3executable in the 3.11.2 installation for Windows 64-bit.Linked PRs