Index: docs/modpython.txt
===================================================================
--- docs/modpython.txt	(revision 6782)
+++ docs/modpython.txt	(working copy)
@@ -114,6 +114,8 @@
 When deploying Django sites on mod_python, you'll need to restart Apache each
 time you make changes to your Python code.
 
+.. _mod_python documentation: http://modpython.org/live/current/doc-html/directives.html
+
 Multiple Django installations on the same Apache
 ================================================
 
@@ -166,16 +168,27 @@
 revoke your Django privileges.
 
 If you're the type of programmer who debugs using scattered ``print``
-statements, note that ``print`` statements have no effect in mod_python; they
-don't appear in the Apache log, as one might expect. If you have the need to
-print debugging information in a mod_python setup, either do this::
+statements, note that writing to ``stdout`` with a regular ``print`` statement
+is a bad idea.  Things written in this fashion will not appear in the Apache
+log and may, with some WSGI hosting solutions, end up corrupting valid
+output sent back to the client.
 
-    assert False, the_value_i_want_to_see
+If you have the need to print debugging information in a mod_python setup,
+then you have three options.  The first is to print to ``stderr`` explicitly,
+like so::
 
-Or add the debugging information to the template of your page.
+    print >> sys.stderr, 'debug text'
+    sys.stderr.flush()
 
-.. _mod_python documentation: http://modpython.org/live/current/doc-html/directives.html
+Note that ``stderr`` is buffered, so calling ``flush`` is necessary if you
+wish debugging information to be displayed promptly.
 
+A second, more compact approach is to use an assertion::
+
+    assert False, 'debug text'
+
+The third option is to add debugging information to the template of your page.
+
 Serving media files
 ===================