view doc/debugging.txt @ 7277:41b2a0e12899

Formatting fixes Fix some blocks that should be code blocks but weren't. Use smaller type for larger/wide code blocks by replacing: stuff:: wide code here with: stuff: .. code:: :class: big-code wide code here The big-code class uses a smaller font size so it fits the width of the page without overflow. Fix an ordered list that was indented more than it should have been.
author John Rouillard <rouilj@ieee.org>
date Mon, 24 Apr 2023 23:26:18 -0400
parents a635a60ffb84
children
line wrap: on
line source

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 -m pytest test/

   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.ini``.

SENDMAILDEBUG
=============

Set to a filename and roundup will write each email message
that it sends to that file instead to the internet. 
This environment variable is independent of the python -O flag.


Roundup Issue Tracker: http://roundup-tracker.org/