Mercurial > p > roundup > code
comparison doc/developers.txt @ 4377:b6f1aaba4827
Small documentation update regarding debugging aids:
- doc/debugging.txt: removed HYPERDBDEBUG and HYPERDBTRACE and
replaced it with the text for SENDMAILDEBUG from doc/developers.txt.
A short code inspection showed that to be correct.
- refered to debugging.txt from developers.txt to have one unique place
for documenting debugging aids.
- Clarified for SENDMAILDEBUG that no email will be send if it is set.
| author | Bernhard Reiter <Bernhard.Reiter@intevation.de> |
|---|---|
| date | Mon, 10 May 2010 07:08:11 +0000 |
| parents | 18cc4323e2ad |
| children | b59ba4dda623 |
comparison
equal
deleted
inserted
replaced
| 4375:378fc1ecaaa6 | 4377:b6f1aaba4827 |
|---|---|
| 95 | 95 |
| 96 | 96 |
| 97 Debugging Aids | 97 Debugging Aids |
| 98 -------------- | 98 -------------- |
| 99 | 99 |
| 100 Try turning on logging of DEBUG level messages. This may be done a number | 100 See `debugging.txt`_. |
| 101 of ways, depending on what it is you're testing: | |
| 102 | |
| 103 1. If you're testing the database unit tests, then set the environment | |
| 104 variable ``LOGGING_LEVEL=DEBUG``. This may be done like so: | |
| 105 | |
| 106 LOGGING_LEVEL=DEBUG python run_tests.py | |
| 107 | |
| 108 This variable replaces the older HYPERDBDEBUG environment var. | |
| 109 | |
| 110 2. If you're testing a particular tracker, then set the logging level in | |
| 111 your tracker's ``config.ini``. | |
| 112 | |
| 113 | 101 |
| 114 Internationalization Notes | 102 Internationalization Notes |
| 115 -------------------------- | 103 -------------------------- |
| 116 | 104 |
| 117 How stuff works: | 105 How stuff works: |