Mercurial > p > roundup > code
diff doc/developers.txt @ 2605:6e9bd67fefa9
complete transition from HYPERDBDEBUG to new logging
| author | Richard Jones <richard@users.sourceforge.net> |
|---|---|
| date | Wed, 21 Jul 2004 00:50:50 +0000 |
| parents | 096063697f77 |
| children | 47766d279878 |
line wrap: on
line diff
--- a/doc/developers.txt Tue Jul 20 23:24:27 2004 +0000 +++ b/doc/developers.txt Wed Jul 21 00:50:50 2004 +0000 @@ -2,7 +2,7 @@ Developing Roundup ================== -:Version: $Revision: 1.11 $ +:Version: $Revision: 1.12 $ .. note:: The intended audience of this document is the developers of the core @@ -107,6 +107,24 @@ consistently check in code which is either broken or takes the codebase in directions that have not been agreed to. + +Debugging Aids +-------------- + +Try turning on logging of DEBUG level messages. This may be done a number +of ways, depending on what it is you're testing: + +1. If you're testing the database unit tests, then set the environment + variable ``LOGGING_LEVEL=DEBUG``. This may be done like so: + + LOGGING_LEVEL=DEBUG python run_tests.py + + This variable replaces the older HYPERDBDEBUG environment var. + +2. If you're testing a particular tracker, then set the logging level in + your tracker's ``config.py``. + + Internationalization Notes --------------------------
