Mercurial > p > roundup > code
view doc/debugging.txt @ 4254:8d3582271a99
Minor update of doc/developers.txt...
...to point to the new resources on www.roundup-tracker.org:
- pointed to the new tracker
- removed references to CVS
- removed "macros": _Roundup CVS, _feature tracker
- hinted at http://www.roundup-tracker.org/code.html and the mailinglist
instead of duplicating information
| author | Bernhard Reiter <Bernhard.Reiter@intevation.de> |
|---|---|
| date | Thu, 17 Sep 2009 09:54:49 +0000 |
| parents | 94e430ad4fdb |
| children | b6f1aaba4827 |
line wrap: on
line source
Debugging Flags --------------- Roundup uses a number of debugging environment variables to help you figure out what the heck it's doing. HYPERDBDEBUG ============ This environment variable should be set to a filename - the hyperdb will write debugging information for various events (including, for instance, the SQL used). This is only obeyed when python is _not_ running in -O mode. HYPERDBTRACE ============ This environment variable should be set to a filename - the hyperdb will write a timestamp entry for various events. This appears to be suffering rather extreme bit-rot and may go away soon. This is only obeyed when python is _not_ running in -O mode. SENDMAILDEBUG ============= Set to a filename and roundup will write a copy of each email message that it sends to that file. This environment variable is independent of the python -O flag.
