lsstDebug.Info raises KeyError

Support
#1

The documentation for lsstDebug says

It is always safe to interrogate lsstDebug; for example lsstDebug.Info(“Robert.Hugh.Lupton”).isBadPerson will return False.

but I am instead finding that I get a KeyError for names that don’t exist:

http://doxygen.lsst.codes/stack/doxygen/x_masterDoxyDoc/base_debug.html

E.g., following the example in the above documentation:

In [1]: import lsstDebug

In [2]:  lsstDebug.Info("Robert.Hugh.Lupton").isBadPerson
---------------------------------------------------------------------------
KeyError                                  Traceback (most recent call last)
<ipython-input-2-3ce450da8355> in <module>()
----> 1 lsstDebug.Info("Robert.Hugh.Lupton").isBadPerson

/Users/wmwv/lsstsw/stack/DarwinX86/base/13.0-4-g0bde1de/python/lsstDebug.pyc in __init__(self, modname)
     51     def __init__(self, modname):
     52         import sys
---> 53         self.__dict__["_dict"] = sys.modules[modname].__dict__
     54         self._modname = modname
     55

KeyError: 'Robert.Hugh.Lupton'

Is this a configuration/install problem on my end, or has there been a change to the behavior away from the documentation?

#2

Is this a configuration/install problem on my end, or has there been a change to the behavior away from the documentation?

Neither, as far as I can tell: the behaviour you see is normal, and the code predates the documentation. The issue seems to be that the latter is simply incorrect (or, at least, misleading). I’ll ticket it.

#3

DM-11125.