finding the source of "interesting" SQL queries

t, an approach that the community would like to include in Django? [1]: http://nedbatchelder.com/blog/201008/global_django_requests.html -- Matt McClure http://www.matthewlmcclure.com http://www.mapmyfitness.com/profile/matthewlmcclure -- You received this message because you are subscri

Re: finding the source of "interesting" SQL queries

Thanks, Russell. That's similar to the approach we were thinking of implementing. Hopefully we'll have a straw man to share shortly. Matt -- You received this message because you are subscribed to the Google Groups "Django developers" group. To view this discussion on the web visit https://g

Avoid unbounded memory consumption when running `manage.py test`

TestSuite holds references to each TestCase instance. So attributes of my TestCase subclasses don't get freed by the garbage collector until the last reference to TestSuite disappears, which isn't until the entire test run ends. In a large test suite, the test run exhausts memory and the OS kill

Re: Avoid unbounded memory consumption when running `manage.py test`

On Friday, July 26, 2013 10:27:23 AM UTC-4, Ramiro Morales wrote: > django.utils.unittest is a copy of the Python>= 2.7 stdlib unittest > library > (aka unittest2) > > Looking at the list of classes involved in your description seems to > indicate > you might want to report your findings to t

Re: Avoid unbounded memory consumption when running `manage.py test`

On Thursday, August 1, 2013 3:50:33 AM UTC-4, Florian Apolloner wrote: > For Python >= 2.7 it should be CPython; for everything below the separate > unittest2 repository. > Thanks. Just closing the loop. Now there's a conversation[1] on python-dev which led to an existing ticket[2] that's alm