References:
* https://docs.djangoproject.com/en/1.8/ref/exceptions/
* https://docs.djangoproject.com/search/?q=http+exception&release=11
* https://docs.djangoproject.com/search/?q=http+error&release=11
--
Ticket URL: <https://code.djangoproject.com/ticket/24359>
Django <https://code.djangoproject.com/>
The Web framework for perfectionists with deadlines.
* needs_better_patch: => 0
* needs_tests: => 0
* needs_docs: => 0
Old description:
> Finding the list of HTTP exceptions via the documentation on any version
> of the Django documentation appears to be challenging.
>
> References:
>
> * https://docs.djangoproject.com/en/1.8/ref/exceptions/
> * https://docs.djangoproject.com/search/?q=http+exception&release=11
> * https://docs.djangoproject.com/search/?q=http+error&release=11
New description:
Finding the list of HTTP exceptions via the documentation on any version
of the Django documentation appears to be challenging.
References:
* https://docs.djangoproject.com/en/1.8/ref/exceptions/#http-exceptions
(location of problematic statement)
* https://docs.djangoproject.com/search/?q=http+exception&release=11
* https://docs.djangoproject.com/search/?q=http+error&release=11
--
--
Ticket URL: <https://code.djangoproject.com/ticket/24359#comment:1>
Comment (by timgraham):
The only documented exception seems to be `UnreadablePostError`. I guess
we might add things like `RawPostDataException` and `MultiPartParserError`
although we'd have to confirm there is a case for using them in code
outside of Django itself.
The sentence "Http exceptions are provided in django.http." means that you
can import the exceptions in this section from there, not that the linked
page has information about them (like the rest of the sections on that
page, but maybe this needs to be clarified... we could remove the links I
suppose).
We are trying to [https://github.com/django/djangoproject.com/pull/303
redo the docs search using ElasticSearch] if useless search results is
part of your complaint.
--
Ticket URL: <https://code.djangoproject.com/ticket/24359#comment:2>
* has_patch: 0 => 1
* stage: Unreviewed => Accepted
Comment:
[https://github.com/django/django/pull/4187 PR] -- feedback welcome. We
can create a separate ticket about documenting those other exceptions if
needed.
--
Ticket URL: <https://code.djangoproject.com/ticket/24359#comment:3>
* status: new => closed
* resolution: => fixed
Comment:
In [changeset:"2b19b3a031e7d5b5264bc9e880d0192301289bc2"]:
{{{
#!CommitTicketReference repository=""
revision="2b19b3a031e7d5b5264bc9e880d0192301289bc2"
Fixed #24359 -- Cleaned up docs/ref/exceptions.html
}}}
--
Ticket URL: <https://code.djangoproject.com/ticket/24359#comment:4>
Comment (by Tim Graham <timograham@…>):
In [changeset:"9d6f0dce139b5dc9ee019f16623e12c6579b45e3"]:
{{{
#!CommitTicketReference repository=""
revision="9d6f0dce139b5dc9ee019f16623e12c6579b45e3"
[1.8.x] Fixed #24359 -- Cleaned up docs/ref/exceptions.html
Backport of 2b19b3a031e7d5b5264bc9e880d0192301289bc2 from master
}}}
--
Ticket URL: <https://code.djangoproject.com/ticket/24359#comment:5>
Comment (by asfaltboy):
I have [https://github.com/spookylukey/django-paypal/issues/79 a use case
for adding RawPostDataException] . I feel it would have helped me greatly
if Django had
[https://github.com/django/django/blob/46338296aa292aa31e329559c561a010a197c2aa/django/http/request.py#L35-L39
this docstring] in the
[https://docs.djangoproject.com/en/1.8/ref/exceptions/#http-exceptions
Http Exceptions documenation] (or even a mention in the
[https://docs.djangoproject.com/en/1.9/ref/request-
response/#django.http.HttpRequest HttpRequest docs]).
Shall I open a new ticket or can we add a patch here?
--
Ticket URL: <https://code.djangoproject.com/ticket/24359#comment:6>
Comment (by timgraham):
New ticket please.
--
Ticket URL: <https://code.djangoproject.com/ticket/24359#comment:7>