#5677: Debugging with mod_python (apache)
----------------------------------------------------------------------+-----
Reporter: Manfred Wassmann <man...@ncc-1701.b.shuttle.de> |
Owner: nickefford
Status: new |
Milestone:
Component: Documentation |
Version: SVN
Resolution: |
Keywords: mod_python
Stage: Accepted |
Has_patch: 1
Needs_docs: 0 |
Needs_tests: 0
Needs_better_patch: 0 |
----------------------------------------------------------------------+-----
Changes (by kmtracey):
* stage: Ready for checkin => Accepted
Comment:
I do not like the current patch's inclusion of a vague reference to
corrupting client output in "some WSGI hosting solutions". This is text
going into the page describing mod_python deployment, specifically. It
should limit itself to what happens under mod_python. Sure, adding prints
to stdout is a bad idea in other hosting environments too, but that's
irrelevant to someone trying to figure out how to debug a problem under
mod_python and more likely to cause confusion than anything else.
--
Ticket URL: <http://code.djangoproject.com/ticket/5677#comment:13>
Django <http://code.djangoproject.com/>
The Web framework for perfectionists with deadlines.
--
You received this message because you are subscribed to the Google Groups
"Django updates" group.
To post to this group, send email to django-upda...@googlegroups.com.
To unsubscribe from this group, send email to
django-updates+unsubscr...@googlegroups.com.
For more options, visit this group at
http://groups.google.com/group/django-updates?hl=en.
