#30102: Optimize the `page_not_found` view after #30070
-------------------------------------+-------------------------------------
Reporter: Illia Volochii | Owner: nobody
Type: | Status: closed
Cleanup/optimization |
Component: Core (Other) | Version: master
Severity: Normal | Resolution: wontfix
Keywords: | Triage Stage:
| Unreviewed
Has patch: 0 | Needs documentation: 0
Needs tests: 0 | Patch needs improvement: 0
Easy pickings: 0 | UI/UX: 0
-------------------------------------+-------------------------------------
Changes (by Carlton Gibson):
* status: new => closed
* resolution: => wontfix
Comment:
As per [https://github.com/django/django/pull/10841 discussion on the
original PR], there are test cases relying on the template context being
available on the response. Working around this ~~probably~~ isn't worth
the effort. [https://github.com/django/django/pull/10855 Follow-up PR]
adds a comment explaining the usage, as per Tim's suggestion.
--
Ticket URL: <https://code.djangoproject.com/ticket/30102#comment:2>
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/065.4a0393d752146f22ed3e88efe266fcc8%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.
