Comment (by claudep):
#22320 was a duplicate with a patch. I think the idea is good, however I'm
a bit worried about the memory consumption, even if production sites
should not be affected. IMO, fixing #12581 is a prerequisite to this one.
--
Ticket URL: <https://code.djangoproject.com/ticket/9363#comment:5>
Django <https://code.djangoproject.com/>
The Web framework for perfectionists with deadlines.
Comment (by claudep):
Patch for #22320 is
https://github.com/mbox/django/commit/c0a5fa22770b90d3ad0fd24ee80b93bebe03fbec
--
Ticket URL: <https://code.djangoproject.com/ticket/9363#comment:6>
* has_patch: 0 => 1
--
Ticket URL: <https://code.djangoproject.com/ticket/9363#comment:7>
* status: new => closed
* resolution: => wontfix
Comment:
This feature is provided by the Django Debug Toolbar. It even works for
templates. If you need this feature, just install the Debug Toolbar.
I know what the code looks like, and I'd rather leave it up to third-
parties...
--
Ticket URL: <https://code.djangoproject.com/ticket/9363#comment:8>
Comment (by mbox):
Django debug toolbar doesn't help for any situation where you're not
running via a web browser, or in a non-request cycle. So for example, any
test case that uses assertNumQueries (see #22320 for example)
The patch for this is a simple few lines, so I don't understand your
concern about "what the code looks like"
--
Ticket URL: <https://code.djangoproject.com/ticket/9363#comment:9>