dogtail-devel [Bug 345734] New: Should Dogtail use the standard PEP282 logging module rather than define its own
- From: "dogtail (bugzilla.gnome.org)" <bugzilla-daemon bugzilla gnome org>
- To: dogtail-devel-list gnome org
- Subject: dogtail-devel [Bug 345734] New: Should Dogtail use the standard PEP282 logging module rather than define its own
- Date: Fri, 23 Jun 2006 06:48:27 -0400 (EDT)
Do not reply to this via email (we are currently unable to handle email
responses and they get discarded). You can add comments to this bug at
http://bugzilla.gnome.org/show_bug.cgi?id=345734
dogtail | Framework | Ver: CVS HEAD
Summary: Should Dogtail use the standard PEP282 logging module
rather than define its own
Product: dogtail
Version: CVS HEAD
Platform: Other
OS/Version: All
Status: UNCONFIRMED
Severity: normal
Priority: Normal
Component: Framework
AssignedTo: dogtail-maint gnome bugs
ReportedBy: dmalcolm redhat com
QAContact: dogtail-maint gnome bugs
GNOME version: Unspecified
GNOME milestone: Unspecified
Please describe the problem:
Dogtail has its own logging.py module.
A "logging" module was added as a result of PEP 282 to Python 2.3:
http://www.python.org/dev/peps/pep-0282/
API docs are here:
http://www.python.org/doc/current/lib/module-logging
Should we simply recommend the use of this module? This has a
"logging.foo()" API, rather than a "log.foo()" API. Ideally we'd like
timestamps as well.
Steps to reproduce:
Actual results:
Expected results:
Does this happen every time?
Other information:
--
Configure bugmail: http://bugzilla.gnome.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are watching the QA contact for the bug.
You are watching the assignee for the bug.
[
Date Prev][
Date Next] [
Thread Prev][
Thread Next]
[
Thread Index]
[
Date Index]
[
Author Index]