Reading through the code in `python do` implementation I am not sure the `python do` block is enough, because net-snmp is compiling native C bindings to use inside of Python, and I think the configure script is using things it retrieves from Python to decide how to compile the bindings, and the `python do` only seems to cover the install path and not the compilation process. Is it palatable to put their whole build inside of `python do`, even when someone has chosen not to use the optional Python bindings? Not sure of the best way to structure this.

Another proposal:

          ENV['PYTHONPROG'] = "#{prefix}/bin/python"