Skip to content
Projects
Groups
Snippets
Help
Loading...
Help
Support
Keyboard shortcuts
?
Submit feedback
Contribute to GitLab
Sign in / Register
Toggle navigation
Z
ZODB
Project overview
Project overview
Details
Activity
Releases
Repository
Repository
Files
Commits
Branches
Tags
Contributors
Graph
Compare
Issues
0
Issues
0
List
Boards
Labels
Milestones
Merge Requests
0
Merge Requests
0
CI / CD
CI / CD
Pipelines
Jobs
Schedules
Analytics
Analytics
CI / CD
Repository
Value Stream
Wiki
Wiki
Snippets
Snippets
Members
Members
Collapse sidebar
Close sidebar
Activity
Graph
Create a new issue
Jobs
Commits
Issue Boards
Open sidebar
Kirill Smelkov
ZODB
Commits
3f571679
Commit
3f571679
authored
Apr 13, 2004
by
Fred Drake
Browse files
Options
Browse Files
Download
Email Patches
Plain Diff
update the module docstring
parent
ffc10179
Changes
1
Hide whitespace changes
Inline
Side-by-side
Showing
1 changed file
with
9 additions
and
15 deletions
+9
-15
trunk/src/zLOG/__init__.py
trunk/src/zLOG/__init__.py
+9
-15
No files found.
trunk/src/zLOG/__init__.py
View file @
3f571679
...
...
@@ -14,6 +14,12 @@
"""General logging facility
Note:
This module exists only for backward compatibility. Any new code
for Zope 2.8 and newer should use the logging module from Python's
standard library directly. zLOG is only an API shim to map existing
use of zLOG onto the standard logging API.
This module attempts to provide a simple programming API for logging
with a pluggable API for defining where log messages should go.
...
...
@@ -47,12 +53,9 @@ The module defines several standard severities:
PANIC=300 -- We're dead!
Also, logging facilities will normally ignore negative severities.
To plug in a log handler, simply replace the log_write function
with a callable object that takes 5 arguments:
subsystem -- The subsystem generating the message (e.g. ZODB)
severity -- The "severity" of the event. This may be an integer or
...
...
@@ -69,18 +72,9 @@ with a callable object that takes 5 arguments:
traceback. If provided, then a summary of the error
is added to the detail.
There is a default event logging facility that:
- swallows logging information by default,
- outputs to sys.stderr if the environment variable
EVENT_LOG_FILE is set to an empty string, and
- outputs to file if the environment variable
EVENT_LOG_FILE is set to a file name.
- Ignores errors that have a severity < 0 by default. This
can be overridden with the environment variable EVENT_LOG_SEVERITY
The default logging facility uses Python's logging module as a
back-end; configuration of the logging module must be handled
somewhere else.
"""
from
EventLogger
import
log_write
,
log_time
,
severity_string
...
...
Write
Preview
Markdown
is supported
0%
Try again
or
attach a new file
Attach a file
Cancel
You are about to add
0
people
to the discussion. Proceed with caution.
Finish editing this message first!
Cancel
Please
register
or
sign in
to comment