>apt remove followed by apt install did fix the problem. Sorry I did not
try that earlier. I do not know what could have been the problem.
I don't know either. I suspect that "something" deleted the binary, but
I wouldn't really know where to look to figure out what. So unless this
happened really recently, I think it will be a needle in the haystack to
find something in the apt logs.
I'm closing this for now, based on your latest comment. If you do happen
to find out the underlying cause, please report a new bug for this.
** Changed in: python-pip (Ubuntu)
Status: New => Invalid
** Changed in: command-not-found (Ubuntu)
Status: New => Invalid
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1779564
Title:
pip3 installation does not give expected result
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/command-not-found/+bug/1779564/+subscriptions
--
ubuntu-bugs mailing list
[email protected]
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
