Browse files

Fixed #5677 -- update modpython stdout documentation. Thanks to Manf…

…red Wassmann for the report, nickefford for the initial patch and Graham Dumpleton for the expert advice.

git-svn-id: bcc190cf-cafb-0310-a4f2-bffc1f526a37
  • Loading branch information...
DrMeers committed Oct 9, 2010
1 parent b7a73cf commit c93f5e5d0e530203048ddb6424ef43acabe17cf1
Showing with 18 additions and 6 deletions.
  1. +18 −6 docs/howto/deployment/modpython.txt
@@ -158,6 +158,8 @@ the full URL.
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:
Multiple Django installations on the same Apache
@@ -211,15 +213,25 @@ everything for each request. But don't do that on a production server, or we'll
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 output to ``stdout`` will not appear in the Apache
+log and can even `cause response errors`_.
- assert False, the_value_i_want_to_see
+.. _cause response errors:
-Or add the debugging information to the template of your page.
+If you have the need to print debugging information in a mod_python setup, you
+have a few options. You can print to ``stderr`` explicitly, like so::
+ print >> sys.stderr, 'debug text'
+ sys.stderr.flush()
+(note that ``stderr`` is buffered, so calling ``flush`` is necessary if you wish
+debugging information to be displayed promptly.)
+A more compact approach is to use an assertion::
-.. _mod_python documentation:
+ assert False, 'debug text'
+Another alternative is to add debugging information to the template of your page.
Serving media files

0 comments on commit c93f5e5

Please sign in to comment.