Warning: Can't synchronize with repository "(default)" (Unsupported version control system "svn": No module named svn). Look in the Trac log for more information.

Ticket #506 (closed task: wontfix)

Opened 13 years ago

Last modified 9 years ago

clarify TurboGears logging guidelines

Reported by: Max Owned by: anonymous
Priority: normal Milestone: 1.0.x bugfix
Component: TurboGears Version:
Severity: normal Keywords: logging


TurboGears uses logging both to help troubleshoot the framework itself and to notify user of important events. There is nothing wrong with this. OTOH, user should have the option to mute framework logging and be reasonably sure that this won't result in important messages being ignored.

To be able to do this, there should be a documented policy that is obeyed by the framework authors. E.g. use DEBUG level for information that is of interest to framework developers and INFO and up for information that may be of interest to framework users. Or, use DEBUG/INFO for "internal" use and WARNING and upper levels to communicate with user.

See  discussion.

Change History

comment:1 Changed 13 years ago by Max <ischenko@…>

Example configuration to mute TG logging:

    import logging
    logger = logging.getLogger('turbokid')
    logger = logging.getLogger('turbogears.visit')
    logger = logging.getLogger('turbogears.identity')

comment:2 Changed 13 years ago by max

  • Type changed from defect to task

Also, the framework can/should provide a configuration option to mute framework's debugging output. This way the user won't be concerned about particular levels framework uses as long as s/he can mute it.

comment:3 Changed 13 years ago by jorge.vargas

  • Component changed from Docs to TurboGears

for the docs http://trac.turbogears.org/turbogears/wiki/logging

as the request that's not a docs topic.

although i'm not sure if this is deployment,instalation or general turbogears issue.

comment:4 Changed 13 years ago by jorge.vargas

  • Milestone changed from 0.9 to 1.0

comment:5 Changed 12 years ago by alberto

  • Milestone changed from 1.0 to 1.1

comment:6 Changed 12 years ago by alberto

  • Milestone changed from 1.1 to __unclassified__

Batch moved into unclassified from 1.1 to properly track progress on the later

comment:7 Changed 11 years ago by khorn

Noone has really done anything with this ticket for a year and a half.

Can it be closed?

comment:8 Changed 10 years ago by jorge.vargas

  • Status changed from new to closed
  • Resolution set to wontfix

comment:9 Changed 9 years ago by chrisz

  • Milestone changed from __unclassified__ to 1.0.x bugfix
Note: See TracTickets for help on using tickets.