Hello, As I mentioned in #6308, some objects seems to be heaping in QueryDict class on calling __deepcopy__ method (via request.POST.copy()).
Then, I'd like to ask guys who are using request.POST.copy in your project that if you have experienced growing process size. Or if you know some way to handle request.POST.copy() without heaping objects (possibly right way to saving POST data for future request), please, let me know. Thanks. -- Yasushi Masuda http://ymasuda.jp/ --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Django users" group. To post to this group, send email to django-users@googlegroups.com 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 -~----------~----~----~----~------~----~------~--~---
