summaryrefslogtreecommitdiff
diff options
context:
space:
mode:
authorLars Wirzenius <liw@liw.fi>2011-05-18 07:38:33 +0100
committerLars Wirzenius <liw@liw.fi>2011-05-18 07:38:33 +0100
commit907781d637e76f1cf520689650d17a0001edf304 (patch)
treeb2212c0e7e3503de2b9ab02d0b3a238ea5df97b3
parentaf3c9c3adac3b47fe3291c95da289082a0855c1b (diff)
downloadpython-tracing-907781d637e76f1cf520689650d17a0001edf304.tar.gz
Update description in setup.py.
-rw-r--r--setup.py16
1 files changed, 10 insertions, 6 deletions
diff --git a/setup.py b/setup.py
index 8a97140..a1789f3 100644
--- a/setup.py
+++ b/setup.py
@@ -24,13 +24,17 @@ setup(name='tracing',
url='http://liw.fi/tracing/',
description='debug log/trace messages',
long_description='''\
-This package provides a couple of functions for logging debug messages.
-It is sometimes practical to add a lot of debugging log messages to a
-program, but having them enabled all the time results in very large
-log files. Also, logging that much takes quite a bit of time.
+This library provides a function for logging debug messages.
+It is sometimes practical during software development to add a lot of
+debugging log messages to a program, but having them enabled all the time
+results in very large log files. Also, logging that much takes quite a
+bit of time.
-This module provides a way to turn such debugging or tracing messages
-on and off, based on the filename they occur in.
+This module provides a way to turn such debugging (or tracing) messages
+on and off, based on the filename they occur in. It is much faster than
+using `logging.Filter` to accomplish the same thing, which matters
+when code is run in production mode. The actual logging still happens
+using the `logging` library.
''',
classifiers=[
'Development Status :: 4 - Beta',