On 26 April 2018 at 21:18, Terry Reedy wrote:
>> If my memory is correct, this is the default for path directories.
>
> The Python entries do, as added by the Windows Installer written by a
> Microsoft engineer, so this must at least be a correct alternative.
It's definitely acceptable - there's
On 4/26/2018 3:04 PM, Virgil Stokes wrote:
However, each entry in this Windows 10 path has a trailing backslash.
Some do, and some don't, which is the same on my Win10
If my memory is correct, this is the default for path directories.
The Python entries do, as added by the Windows Installe
On 26 April 2018 at 20:04, Virgil Stokes wrote:
> IMHO it would have been useful to have "warning" somewhere in these
> messages.
Ha, I'd never even noticed that it didn't...
I think it's in a different colour, FWIW, but your point is good.
Paul
--
https://mail.python.org/mailman/listinfo/pytho
Thanks Paul for the prompt reply,
However, each entry in this Windows 10 path has a trailing backslash. If
my memory is correct, this is the default for path directories.
IMHO it would have been useful to have "warning" somewhere in these
messages.
On 2018-04-26 20:52, Paul Moore wrote:
On
On 26 April 2018 at 19:33, Virgil Stokes wrote:
> Why am I getting this message, that I need to consider adding this directory
> to PATH when it is already in PATH?
> Note, all of these *.exe files are in C:\Python36\Scripts.
The PATH entry ends with a backslash, which is confusing the check
done
First I upgraded my pip
*C:\Python36>python -m pip install --upgrade pip*
Collecting pip
Downloading
https://files.pythonhosted.org/packages/0f/74/ecd13431bcc456ed390b44c8a6e917c1820365cbebcb6a8974d1cd045ab4/pip-10.0.1-py2.py3-none-any.whl
(1.3MB)
100% ||
