Personally I'd be in favour of adding such classes. It seems against the batteries-included philosophy that Django does not provide all of the standard codes as classes. I can never remember which codes correspond to which response types, if I saw status=204 in code it would be a 'magic number' for me and I'd have to look it up. HttpResponseRedirect and HttpResponsePermanentRedirect have been my friends in the past, I can imagine the same for HttpResponseNoContent.
On 7 April 2017 at 00:44, Philip Lee <redstone-c...@163.com> wrote: > I think you'd better write the decision in the document to stop Django > users from making the same feature request in future ! > > On Thursday, April 6, 2017 at 12:35:41 AM UTC+8, Tim Graham wrote: >> >> Hi, this was already wontfixed here: >> https://code.djangoproject.com/ticket/3362 >> >> with the rationale, "We've decided in the past not to add a new class for >> every single response code. You can already pass the status code in when >> creating the HttpResponse class, so that can be used in this case." >> >> (found with this google search: httpresponse 204 site: >> code.djangoproject.com) >> >> On Wednesday, April 5, 2017 at 11:25:44 AM UTC-4, Philip Lee wrote: >>> >>> Every Django view function MUST return an HttpResponse object, sometimes we >>> just want to send data to the server and don't want to send data back to >>> the client , this probably lead Python users want to return None instead, >>> however , this is not allowed in Django view function, I found >>> HttpResponse(status=204) >>> <https://www.w3.org/Protocols/rfc2616/rfc2616-sec10.html#sec10> may come >>> for rescue in this case, thus it would be better to include >>> HttpResponse(status=204) as an HttpResponse subclasses for convenience so >>> that could save Django users from asking those returning-null-response >>> questions:http://stackoverflow.com/questions/17557618/post-without-response-in-django-javascript-interactionhttp://stackoverflow.com/questions/2131203/django-no-redirectionshttp://stackoverflow.com/questions/4123155/how-do-i-send-empty-response-in-django-without-templates >>> >>> BTW, someone already implemented this feature here, better to adopt it in >>> Django http://django-extras.readthedocs.io/en/latest/ref/http-response.html >>> >>> -- > You received this message because you are subscribed to the Google Groups > "Django developers (Contributions to Django itself)" group. > To unsubscribe from this group and stop receiving emails from it, send an > email to django-developers+unsubscr...@googlegroups.com. > To post to this group, send email to django-developers@googlegroups.com. > Visit this group at https://groups.google.com/group/django-developers. > To view this discussion on the web visit https://groups.google.com/d/ > msgid/django-developers/2f619780-d6f1-4bce-8d34- > 40a18b87d798%40googlegroups.com > <https://groups.google.com/d/msgid/django-developers/2f619780-d6f1-4bce-8d34-40a18b87d798%40googlegroups.com?utm_medium=email&utm_source=footer> > . > > For more options, visit https://groups.google.com/d/optout. > -- Adam -- You received this message because you are subscribed to the Google Groups "Django developers (Contributions to Django itself)" group. To unsubscribe from this group and stop receiving emails from it, send an email to django-developers+unsubscr...@googlegroups.com. To post to this group, send email to django-developers@googlegroups.com. Visit this group at https://groups.google.com/group/django-developers. To view this discussion on the web visit https://groups.google.com/d/msgid/django-developers/CAMyDDM3mrxWg4tW6CTYKMCxU4Fsk8Fs55uEVtEN6gR-yAw2QOw%40mail.gmail.com. For more options, visit https://groups.google.com/d/optout.
