That indeed did the trick. I new it would be something embarrassingly simple.
Thank you very much, James. Much obliged. -Alex. On Dec 18, 11:06 am, "James Bennett" <[EMAIL PROTECTED]> wrote: > On Dec 18, 2007 9:57 AM, [EMAIL PROTECTED] > > <[EMAIL PROTECTED]> wrote: > > That's really all it does. If you watch it in top, however, python's > > memory consumption rises steadily as the file is processed (f is very > > large, so there are many iterations of the loop). I was wondering if > > anyone knew where all this memory was going? Is django spawning > > objects under the hood somewhere that I need to explicitly delete? > > Forgive me if this is a too-simple question, but I have been unable to > > figure it out thus far. > > You have DEBUG=True in your settings file, which means that, for > debugging purposes, Django is keeping an in-memory list of database > queries it has performed. This list naturally grows in size with each > successive query. To disable this, set DEBUG=False. > > -- > "Bureaucrat Conrad, you are technically correct -- the best kind of correct." --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Django users" group. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/django-users?hl=en -~----------~----~----~----~------~----~------~--~---
