Installation of tensorflow via pip -- messages?

[Virgil Stokes]

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% |████████████████████████████████| 1.3MB 685kB/s
Installing collected packages: pip
  Found existing installation: pip 9.0.3
    Uninstalling pip-9.0.3:
      Successfully uninstalled pip-9.0.3
Successfully installed pip-10.0.1

Then I upgraded tensorflow

*C:\Python36>python -m pip install --upgrade tensorflow*
...
...
...
The script tensorboard.exe is installed in 'C:\Python36\Scripts' which
is not on PATH.
  Consider adding this directory to PATH or, if you prefer to suppress
this warning, use --no-warn-script-location.

...
...

The scripts freeze_graph.exe, saved_model_cli.exe, tensorboard.exe,
toco.exe and toco_from_protos.exe are installed in 'C:\Python36\Scripts'
which is not on PATH.
  Consider adding this directory to PATH or, if you prefer to suppress
this warning, use --no-warn-script-location.

However, this directory is in my PATH

*C:\Python36>path*
PATH=C:\Program Files (x86)\Common Files\Oracle\Java\javapath;C:\Program
Files (x86)\Intel\iCLS
Client\;C:\Python36\Scripts\;C:\Python36\;C:\ProgramData\Oracle\Java\javapath;C:\Program
Files (x86)\Common Files\Intel\Shared Files\cpp\bin\Intel64;C:\Program
Files\Intel\iCLS
Client\;C:\windows\system32;C:\windows;C:\windows\System32\Wbem;C:\windows\System32\WindowsPowerShell\v1.0\;C:\Program
Files (x86)\NVIDIA Corporation\PhysX\Common;C:\Program Files\MiKTeX
2.9\miktex\bin\x64\;
...
...

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.

[Paul Moore]

On 26 April 2018 at 19:33, Virgil Stokes <v...@it.uu.se> 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 by pip. It's a known issue and has been fixed in the development
version of pip, so it'll be resolved in the next release. In the
meantime, you can either remove the redundant trailing backslash from
your PATH, or just ignore the warning.

Paul

[Virgil Stokes]

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.

[Paul Moore]

On 26 April 2018 at 20:04, Virgil Stokes <v...@it.uu.se> 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

[Terry Reedy]

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 Installer written by a
Microsoft engineer, so this must at least be a correct alternative.

--
Terry Jan Reedy

[Paul Moore]

On 26 April 2018 at 21:18, Terry Reedy <tjr...@udel.edu> 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 no doubt the pip 10.0.1 behaviour
is a bug (that's been fixed). No-one is arguing otherwise. The
suggestion to remove the backslashes was nothing more than a
workaround that can be used until the next release of pip.

Paul