[Django] #21136: Show Tracebacks to a certain set of users
Django
------------------------------+--------------------
Reporter: lorenz-dev@… | Owner: nobody
Type: New feature | Status: new
Component: Core (Other) | Version: 1.5
Severity: Normal | Keywords:
Triage Stage: Unreviewed | Has patch: 0
Easy pickings: 0 | UI/UX: 0
------------------------------+--------------------
I'd like to be able to configure DEBUG a bit further. Well, not really.
I'd like something like the ADMINISTRATORS setting to configure which
users to show tracebacks to.
To explain a bit further, here's my usecase: We have written a network
management tool that is used both by the network administrators and the
users. Users can see their status, terminate their contract, etc.
Administrators create contracts, assign subnets, handle payments, and so
on. Each of our developers is also an administrator, and all
administrators have a rough understanding of how the software does things.
We're not super-professional or anything and it's a rather large project,
so bugs happen. No we obviously can't just enable DEBUG - that would be
moronic. But we do want the administrators to see the tracebacks they
cause. We can't, however, put them all in the ADMINISTRATORS setting,
because the tracebacks often contain sensitive information. Therefore,
we'd like to be able to configure, e.g. via the permissions system, to
whom tracebacks are shown. Does that make it clear?
--
Ticket URL: <https://code.djangoproject.com/ticket/21136>
Django <https://code.djangoproject.com/>
The Web framework for perfectionists with deadlines.
Django
Reporter: lorenz-dev@… | Owner: nobody
Type: New feature | Status: closed
Component: Core (Other) | Version: 1.5
Keywords: | Triage Stage: Unreviewed
Has patch: 0 | Needs documentation: 0
Needs tests: 0 | Patch needs improvement: 0
Easy pickings: 0 | UI/UX: 0
Changes (by timo):
* status: new => closed
* needs_better_patch: => 0
* resolution: => wontfix
* needs_tests: => 0
* needs_docs: => 0
Comment:
You can do this with some custom middleware
[http://ericholscher.com/blog/2008/nov/15/debugging-django-production-
environments.html like this]. I'm not sure if including something like
this in Django core has been discussed before, but I feel like each use
case may be a bit different, so letting third parties implement their own
solution makes sense.
--
Ticket URL: <https://code.djangoproject.com/ticket/21136#comment:1>
Django
Reporter: lorenz-dev@… | Owner: nobody
Type: New feature | Status: closed
Component: Core (Other) | Version: 1.5
Keywords: | Triage Stage: Unreviewed
Has patch: 0 | Needs documentation: 0
Easy pickings: 0 | UI/UX: 0
Comment (by lorenz-dev@…):
Wow, thank you, that is very much what we want to do. I didn't know this
was even possible, but seeing as it is, wontfix sounds right. Thank you
again.
--
Ticket URL: <https://code.djangoproject.com/ticket/21136#comment:2>