Scripts like qdstat currently load the qpid_python_internal module in a special way by using the value of the env. var QPID_DISPATCH_HOME. This is very weird and surprising. It creates havoc if you have multiple installs or builds of dispatch and assume that you just need to set PYTHONPATH to make things work.
The normal way to locate python modules is via PYTHONPATH. I propose we treat qpid_python_internal like any other python module, install it in the standard place by default and let users just set PYTHONPATH to pick up all the python bits they need. I don't see any reason why it needs special treatment. The name makes it pretty obvious that it is an internal module and not for general use (maybe _private would be clearer?) Any objections? Cheers, Alan. --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
