Changes between Initial Version and Version 1 of Ticket #28469


Ignore:
Timestamp:
Aug 9, 2017, 5:19:37 PM (7 years ago)
Author:
Tim Graham
Comment:

As I mentioned on the mailing list, I don't think we should add subclasses if they don't provide any functionality besides a different status code. For that, we could document this pattern: 

from http import HTTPStatus
HttpResponse(status=HTTPStatus.NO_CONTENT)

If a response subclass provides some other additional functionality, I'm open to adding it.

Legend:

Unmodified
Added
Removed
Modified

  • Ticket #28469

    • Property Triage Stage Unreviewed → Accepted
    • Property Summary Add "missing" response type subclasses → Add additional response type subclasses

  • Ticket #28469 – Description

    initial v1  
    1 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
    2 , HttpResponseNoContent in #3362, etc.
     1In 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.
    32
    4 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 .
     3[https://groups.google.com/forum/#!msg/django-developers/gnfX1m5jfm8/lMAucX_oBAAJ A recent discussion] on the django-developers mailing list came to the consensus that adding them would be a win. It also pointed out [https://django-extras.readthedocs.io/en/latest/ref/http-response.html  existing implementations in django-extras].
    54
    65They should be added to Django core.
Back to Top