#24868: Invalid kwarg passed to technical_500_response() handling
SuspiciousOperation in debug mode
-------------------------------------+-------------------------------------
Reporter: andrewhayes1979 | Owner: nobody
Type: Bug | Status: closed
Component: Core (URLs) | Version: 1.8
Severity: Normal | Resolution: invalid
Keywords: | Triage Stage:
technical_500_response | Unreviewed
suspiciousoperation |
Has patch: 0 | Needs documentation: 0
Needs tests: 0 | Patch needs improvement: 0
Easy pickings: 1 | UI/UX: 0
-------------------------------------+-------------------------------------
Comment (by andrewhayes1979):
This actually turned out to be an issue in django-extensions, something
called null_technical_500_response()...needs patching there for Django
1.8+.
My bad.
--
Ticket URL: <https://code.djangoproject.com/ticket/24868#comment:3>
Django <https://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 unsubscribe from this group and stop receiving emails from it, send an email
to [email protected].
To post to this group, send email to [email protected].
To view this discussion on the web visit
https://groups.google.com/d/msgid/django-updates/073.277e85fc76d9c64dcf5d6de25ff27b9a%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.
