Which is not to say that "make test_python" yet exists, but if it did, it would depend on "make install_c".

It would be really nice if developing Python GRPC* didn't require root permissions at any point. Unfortunately it seems like all the standard development tools (distutils, virtualenv, and pip, at least for now) steer the developer toward requiring root access and installing system-wide any underlying libraries used by, but not statically linked into, the developer's Python C extension module.

Boo.

This may not be solvable within GRPC; this may only be solvable by enhancements to the tools themselves. It's worth at least investigating though.

*and perhaps all of GRPC, but let's leave that out of scope for this issue