Paul Watson <paul.hermeneu...@gmail.com> 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 exec
Paul Watson <paul.hermeneu...@gmail.com> 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 sy
New submission from Paul Watson <paul.hermeneu...@gmail.com>:
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
comp
New submission from Paul Watson :
The documentation for venv in Python 3.7 references using `python3` to run
venv. I do not find a `python3` executable in the kit.
https://docs.python.org/3.7/library/venv.html#module-venv
--
assignee: docs@python
components: Documentation
messages
New submission from Paul Watson :
Fresh install of 3.9.1
Created venv
Activated venv
(py3.9) 13:12:59.52 C:\venv\py3.9\Scripts
C:>pip search astronomy
ERROR: Exception:
Traceback (most recent call last):
File "c:\venv\py3.9\lib\site-packages\pip\_internal\cli\base_command.py&quo
New submission from Paul Watson :
In the venv .\Scripts directory. the name 'Activate.ps1' does not conform to
the PowerShell prescribed Verb-Noun format.
How about using 'Initialize-Python.ps1' as the script name? Or, something else
that does conform to PowerShell standard naming
