#16238: TECHNICAL_*_TEMPLATE change
-------------------------------------+-------------------------------------
               Reporter:  haras      |          Owner:  nobody
                   Type:  New        |         Status:  new
  feature                            |      Component:  Core (Other)
              Milestone:  1.4        |       Severity:  Normal
                Version:  SVN        |       Keywords:
             Resolution:             |      Has patch:  0
           Triage Stage:  Design     |    Needs tests:  0
  decision needed                    |  Easy pickings:  0
    Needs documentation:  0          |
Patch needs improvement:  0          |
                  UI/UX:  1          |
-------------------------------------+-------------------------------------
Changes (by aaugustin):

 * needs_better_patch:   => 0
 * needs_docs:   => 0
 * needs_tests:   => 0
 * stage:  Unreviewed => Design decision needed


Comment:

 The discussion on the mailing list didn't reach a consensus. Apparently,
 the current page is not that bad :) (except for AJAX calls).

 This topic often leads to bikeshedding. A significant improvement from the
 status quo will be necessary to overcome it. I don't think Yet Another
 Setting is an acceptable as a workaround for the lack of community
 support.

 For the record, #11834 and #16227 are subsets of this.

 Note that the 500 template is embedded into the source file for a
 technical reason (see the source), so it's difficult to simply make it
 configurable through the standard template loading mechanism.

 Finally, the Django Debug Toolbar is currently considered for inclusion in
 django.contrib (if there's a ticket, I can't find it). The error page and
 the debug bar are both debug tools, even if they're used in different
 circumstances. Giving them a common look'n'feel could be a way to gather
 support for this change.

-- 
Ticket URL: <https://code.djangoproject.com/ticket/16238#comment:1>
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 post to this group, send email to django-updates@googlegroups.com.
To unsubscribe from this group, send email to 
django-updates+unsubscr...@googlegroups.com.
For more options, visit this group at 
http://groups.google.com/group/django-updates?hl=en.

Reply via email to