Mercurial > p > roundup > code
view doc/debugging.txt @ 2646:fd7b2fc1eb28
Config is now base class for all configurations...
...main Roundup configuration class is CoreConfig.
Builtin TRACKER_HOME renamed to HOME in Config and Options.
In CoreConfig, TRACKER_HOME is an alias for HOME.
Option.value2str(): added parameter 'current' -
stringify current Option value.
Option RDBMS_PORT defaults to None.
Config: added methods add_section, update_option, getopt (not implemented).
Config.save(): added warning about unset options at the top of the file.
new class UserConfig for inifile-driven configs.
CoreConfig: new attributes .ext and .detectors holding UserConfigs
for extensions and detectors, respectively.
| author | Alexander Smishlajev <a1s@users.sourceforge.net> |
|---|---|
| date | Tue, 27 Jul 2004 11:26:20 +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.