I think it should be noted somewhere in documentation that targets like "python-pip" may unintentionally trigger execution of other targets if their names match the command line arguments being used.

For example, let's add this rule to GNUmakefile:

ralc:
	touch $@

Now make python-pip search ralc will trigger both pip invocation and this rule. Using -- doesn't help either, the behavior remains exactly the same. That is the price of the clever hack (linked below): while there is a way to read $(MAKECMDGOALS) there is no way (afaik) to forbid execution of those ARGS as separate targets:

Thanks for creating this project! I like the idea and I use somewhat similar Makefile in my projects :)