silpa-discuss
[Top][All Lists]
Advanced

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

[silpa-discuss] [task #10433] Add a logging component to framework


From: Santhosh Thottingal
Subject: [silpa-discuss] [task #10433] Add a logging component to framework
Date: Sun, 30 May 2010 15:15:40 +0000
User-agent: Mozilla/5.0 (X11; U; Linux i686; ml_IN; rv:1.9.1.9) Gecko/20100414 Iceweasel/3.5.9 (like Firefox/3.5.9)

URL:
  <http://savannah.nongnu.org/task/?10433>

                 Summary: Add a logging component to framework
                 Project: Silpa Indian  Language Processing Project
            Submitted by: santhosh
            Submitted on: Sun May 30 20:45:39 2010
         Should Start On: Sun May 30 00:00:00 2010
   Should be Finished on: Wed Jun 30 00:00:00 2010
                Category: None
                Priority: 5 - Normal
                  Status: None
                 Privacy: Public
        Percent Complete: 0%
             Assigned to: None
             Open/Closed: Open
         Discussion Lock: Any
                  Effort: 0.00

    _______________________________________________________

Details:

Apache +  mod_wsgi has some limitations in using print statements for
debugging(see http://code.google.com/p/modwsgi/wiki/DebuggingTechniques).
Moreover using print statements is not a clean way or logging.

What we need is a logging component , that will write the debug , error, and
such information to a separate log file (or optionally  std.out or std.err)
from the modules, one should able to log like this
from utils import silpa_logger
silpa_logger.info(.....)
silpa_logger.debug(.....)
silpa_logger.error(.....)

Proposed solution: Just write a wrapper over python logging module and make
it available through out the framework.








    _______________________________________________________

Reply to this item at:

  <http://savannah.nongnu.org/task/?10433>

_______________________________________________
  Message sent via/by Savannah
  http://savannah.nongnu.org/




reply via email to

[Prev in Thread] Current Thread [Next in Thread]