Comment 2 for bug 1779564

Thanks for reporting.

The package suggestion comes from the command-not-found package, but I'm not quite sure which is at fault here. (Especially since I am not able to reproduce the issue on my 17.10 system, pip3 runs as expected after installing)

Could you please post the output of the following commands:
1. dpkg -L python3-pip (tells us which files are installed by the package, which should include the pip3 binary)
2. apt policy python3-pip (just to double-check, the version number looks ok from the apport information in the summary)
3. echo $PATH (in case it can't find the binary to run in your PATH, although this sounds a bit unlikely)