#4891 closed (wontfix)
cgitb for mod_python
| Reported by: | Owned by: | nobody | |
|---|---|---|---|
| Component: | HTTP handling | Version: | dev |
| Severity: | Keywords: | ||
| Cc: | Triage Stage: | Design decision needed | |
| Has patch: | yes | Needs documentation: | no |
| Needs tests: | no | Patch needs improvement: | no |
| Easy pickings: | no | UI/UX: | no |
Description
Hi,
here is a small patch to modpython.py and modpython.txt. It allows you
to use cgitb if an error at mod_python level happens. (e.g. Errors in
middleware code). It uses cgitb instead of displaying the simple ascii
traceback.
Attachments (1)
Change History (7)
by , 17 years ago
| Attachment: | modpython.diff added |
|---|
comment:1 by , 17 years ago
comment:2 by , 17 years ago
This patch uses cgitb for errors at mod_python (apache module) level.
Sorry, #4903 is not a duplicate. It is about falling back to cgitb if there
is an error in views/debug.py
comment:3 by , 17 years ago
| Cc: | added |
|---|
comment:4 by , 16 years ago
| Triage Stage: | Unreviewed → Design decision needed |
|---|
comment:5 by , 16 years ago
| Resolution: | → wontfix |
|---|---|
| Status: | new → closed |
I don't much see the point of including this in Django proper -- very few people are going to want cgitb over the pretty error pages, and those few that do can do this themselves.
comment:6 by , 16 years ago
| Cc: | removed |
|---|
Note:
See TracTickets
for help on using tickets.
#4903 is a duplicate, and has an alternate patch.