Oct-18-2017, 06:45 AM
For anyone who read the above post and also didn't know a solution, I now understand it better. The truth is that "downstream modules" really aren't so downstream after all. The modules I imported prior to MainWindow() being called all get parsed to at least some extent, and in one of those local modules I had a call to logging.info() that was placed prior to the __init__() function of a class. The parser apparently tried to process it, but because the configuration command for logging does't get called until I'm in MainWindow.__init__(), it couldn't do anything with it. I wish this kind of thing wasn't a silent failure, but it is.
The solution was to move the import logging command to higher up in the list, and follow it immediately with the logging.basicConfig() command before any of the local modules get imported.
That gives you a lot more flexibility on where to place your other calls to the logging module.
The solution was to move the import logging command to higher up in the list, and follow it immediately with the logging.basicConfig() command before any of the local modules get imported.
That gives you a lot more flexibility on where to place your other calls to the logging module.