Jim Bosch I am rather confused about how this is supposed to be done. I altered the python code in ci_hsc to use lsst.log instead of pex_logging, and in some cases that seemed to work OK. In particular, I used lsst.log.Log.getLogger() to replace the pex_logging getDefaultLog, since the two classes both suppor the log.info, debug, warn, and error signatures which seem to be used by a lot of the underlying code.
However, I see two problems with this approach:
(1) the log which is created seems to sometimes call code which expects the values -1 or -2 to be acceptable values for the log level. I think these were meaningful to pex_logging, but not to lsst,log.
(2) I seem to run into code which is called by ci_hsc which expect to be able to call routine in _loggingLib in pex_logging, even though I am not myself including or calling classes in that Library. That seems to indicate that there is code under ci_hsc which depends on pex_logging, even if ci_hsc does not. Am I supposed to chase down anything called by ci_hsc and remove its dependence on pex_logging? Could involve considerably more modules than ci_hsc.