I've been round and round looking for where the default logging level is set in both the python and client code with no luck.
I went looking since I discovered that not everything is printing out in the logs since (apparently) the logging level is set to 2 (kWarningLevel) by default. To increase my confusion, the C code side levels seem to indicate that the higher the number, the more detail you get while the Python PtDebugPrint() only prints entries >= the logging level. Either I am misreading everything (entirely possible) or the C code and the Python work opposite each other. PtDebugPrint() appears to get the logging level from the C code (PtGetPythonLoggingLevel()). Right now, log entries coded at kDebugDumpLevel (level=1) are not printing for me.
Could someone point out where I am not seeing what the heek is going?
EDIT: and WOW! I changed the criteria for printing debug statements in PlasmaTypes.py to print more detail (essentially reversed it) so at a debug level of 2, everything from level 0 to 2 prints (not cool but definitely causes the log to take a dump
). The way it is currently written, if the default level is 2, then the warn(2) and error(3) levels print. Any statement not encoded with a level gets bumped to 3 and prints as well. Now the question is how exactly should this be written to work? I also found a level 0 setting (kNoLevel) that could be used. And I still need to know where the default level is set. I found the command to set it using the console.
EDIT2: nvm... I found it in cyMisc.cpp... set to 3 if external client and 2 if anything else. Can also be changed through the console.