#24868: Invalid kwarg passed to technical_500_response() handling
SuspiciousOperation in debug mode
-------------------------------------+-------------------------------------
Reporter: andrewhayes1979 | Owner: nobody
Type: Bug | Status: new
Component: Core (URLs) | Version: 1.8
Severity: Normal | Resolution:
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
-------------------------------------+-------------------------------------
Changes (by bmispelon):
* needs_better_patch: => 0
* needs_tests: => 0
* needs_docs: => 0
Comment:
Hi,
Can you show an example of code that triggers the invalid kwarg error?
From what I can tell, `technical_500_response` does take a `status_code`
argument:
https://github.com/django/django/blob/stable/1.8.x/django/views/debug.py#L87
Thanks.
--
Ticket URL: <https://code.djangoproject.com/ticket/24868#comment:1>
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.98d82c540b125b4a5ff8d5a655c1ad71%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.
