A problem we're starting to see on distutils-sig is folks trying to type pip commands into the Python REPL rather than their system shell, and getting cryptic syntax errors back:

>>> pip install requests
  File "<stdin>", line 1
    pip install requests
              ^
SyntaxError: invalid syntax
>>> python -m pip install requests
  File "<stdin>", line 1
    python -m pip install requests
                ^
SyntaxError: invalid syntax

This may be amenable to a similar solution to the one we used to give a custom error message for "print ":

>>> print foo
  File "<stdin>", line 1
    print foo
            ^
SyntaxError: Missing parentheses in call to 'print'

That code currently checks for "print " and "exec ", so it would be a matter of adding another special case that looked for "pip install " appearing anywhere in the string that's failing to compile (it can't be limited to the start as it may be an attempt to invoke pip via "-m")

Paul Moore pointed out on distutils-sig that since this is mainly desired for the REPL, we can put the logic in the default excepthook rather than into the SyntaxError constructor the way we had to for "print" and "exec":

    def excepthook(typ, value, traceback):
        if typ is SyntaxError and "pip install" in value.text:
            print("'pip install' found in supplied text")
            print("Try running this from a system command prompt")
            return
        sys.__excepthook__(typ, value, traceback)

Given that this can be done with just an excepthook change, I'm going to suggest we make the change for 3.5 and 2.7 as well.

I am looking at this, as part of the EuroPython 2018 sprint.

On 3.11:

>>> pip install requests
  File "<stdin>", line 1
    pip install requests
    ^^^^^^^^^^^
SyntaxError: invalid syntax. Perhaps you forgot a comma?

Similar discussion in a newer issue: https://bugs.python.org/issue45721

I closed #45721, which has additional comments, as a duplicate of this.

'print foo' now results in "SyntaxError: Missing parentheses in call to 'print'. Did you mean print(...)?"

I've updated my pull request from 3 years ago. Fixed merge conflicts and addressed all comments. 

https://github.com/python/cpython/pull/8536