Opened 16 years ago

Closed 15 years ago

#309 closed enhancement (fixed)

Consider replacing print statements by logging

Reported by: ole Owned by: rwilson
Priority: low Milestone:
Component: Other Version:
Severity: normal Keywords:
Cc:

Description (last modified by rwilson)

A good idea suggested by several people.

See e.g. ​http://72.14.235.132/search?q=cache:NlCkPdW3rHwJ:blog.tplus1.com/index.php/2007/09/28/the-python-logging-module-is-much-better-than-print-statements/+logging+Python&hl=en&ct=clnk&cd=6&gl=au

Change History (3)

comment:1 Changed 16 years ago by ole

  • Type changed from defect to enhancement

comment:2 Changed 16 years ago by rwilson

  • Description modified (diff)
  • Status changed from new to assigned

A simple module to cater for ANUGA logging has been written at anuga_core/utilities/log.py.

This allows logging to the screen and a logfile, with different loglevels for the screen and logfile. The logfile logging level is forced to be at a lower or equal logging level that that used for the screen, ensuring that anything logged to the screen also goes into the logfile.

An attempt has been made to also write the calling module name and linenumber into the logfile. This only works under python 2.5 or later and fails silently if running earlier versions. This feature works in the test case, but gives wrong information in the real code.

comment:3 Changed 15 years ago by rwilson

  • Resolution set to fixed
  • Status changed from assigned to closed
Note: See TracTickets for help on using tickets.