Which appears after closer examination of the logs to just be an issue with the root logger having an additional handler added to it after Kolibri has been initialized.
Solves this by using a named logger, and holding off on logging until after Kolibri has been initialized.
Fixes #156
Which appears after closer examination of the logs to just be an issue with the root logger having an additional handler added to it after Kolibri has been initialized.
Solves this by using a named logger, and holding off on logging until after Kolibri has been initialized.