#28469: Add "missing" response type subclasses
-------------------------------------------------+------------------------
Reporter: Adam (Chainz) Johnson | Owner: nobody
Type: New feature | Status: new
Component: HTTP handling | Version: 1.11
Severity: Normal | Keywords:
Triage Stage: Unreviewed | Has patch: 0
Needs documentation: 0 | Needs tests: 0
Patch needs improvement: 0 | Easy pickings: 0
UI/UX: 0 |
-------------------------------------------------+------------------------
In the past Django has refused to add more HttpResponse subclasses to
support all the codes listed in the HTTP RFC, e.g. in #9943
, HttpResponseNoContent in #3362, etc.
A recent discussion on the django-developers mailing list (
https://groups.google.com/forum/#!msg/django-
developers/gnfX1m5jfm8/lMAucX_oBAAJ ) came to the consensus that adding
them would be a win. It also pointed out existing implementations in
django-extras, documented at https://django-
extras.readthedocs.io/en/latest/ref/http-response.html .
They should be added to Django core.
--
Ticket URL: <https://code.djangoproject.com/ticket/28469>
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 django-updates+unsubscr...@googlegroups.com.
To post to this group, send email to django-updates@googlegroups.com.
To view this discussion on the web visit
https://groups.google.com/d/msgid/django-updates/053.2c6e4768cc4e78b61c3eecee319d2dec%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.
