Also reducing the priority back to "normal" - the docs at https://docs.python.org/3/installing/ already specifically recommend the "python -m pip" spelling because it's the most universal.

Calling "pip" directly is known to fail in a variety of situations. For example, at system level on *nix systems, it invokes the Python 2 version - you have to call "pip3" to get the Python 3 version. On Windows, if the Scripts directory isn't on PATH, calling pip directly also doesn't work.

This bug just adds another scenario to that existing list.

(I filed https://github.com/pypa/python-packaging-user-guide/issues/107 to suggest also making the "pip -> python -m pip" switch in PyPUG examples)