configglue team mailing list archive

[Anthony Lenton <1012766@xxxxxxxxxxxxxxxxxx>]

Public bug reported:

When reporting warnings configglue uses plain logging.warning() instead
of using a more specific logger.

One standard approach is to use the name of the module that's issuing
the logs (like "configglue.parser"), but any logger other than the root
logger would make it easier to selectively mute or handle configglue's
output.

** Affects: configglue
     Importance: Undecided
         Status: Confirmed

** Changed in: configglue
       Status: New => Confirmed

-- 
You received this bug notification because you are a member of
Configglue developers, which is the registrant for configglue.
https://bugs.launchpad.net/bugs/1012766

Title:
  Logs to root logger

Status in configglue:
  Confirmed

Bug description:
  When reporting warnings configglue uses plain logging.warning()
  instead of using a more specific logger.

  One standard approach is to use the name of the module that's issuing
  the logs (like "configglue.parser"), but any logger other than the
  root logger would make it easier to selectively mute or handle
  configglue's output.

To manage notifications about this bug go to:
https://bugs.launchpad.net/configglue/+bug/1012766/+subscriptions