> 2. Introspect the logging handlers once the config has been loaded and > identify logfiles
This won't work since the exception occurs during the fileConfig() call.
> 2. Introspect the logging handlers once the config has been loaded and
> identify logfiles
This won't work since the exception occurs during the fileConfig() call.