On Sat, May 23, 2009 at 10:34 AM, Andrew Se. Fefelov < andrew.fefe...@gmail.com> wrote:
> > Hello guys! > > Using manage.py loaddata I got error > > RuntimeError: maximum recursion depth exceeded > > Full text on: http://dpaste.com/46940/ > > Don know what to do. Help pls! > >From the stack trace: File "D:\Python25\lib\site-packages\django\db\models\base.py", line 394, in save_base created=(not record_exists), raw=raw) File "D:\Python25\lib\site-packages\django\dispatch\dispatcher.py", line 148, in send response = receiver(signal=self, sender=sender, **named) File "c:\TEMP\ag\ag\stdimage\fields.py", line 102, in _rename_resize_image instance.save() File "D:\Python25\lib\site-packages\django\db\models\base.py", line 311, in save self.save_base(force_insert=force_insert, force_update=force_update) File "D:\Python25\lib\site-packages\django\db\models\base.py", line 394, in save_base created=(not record_exists), raw=raw) Django's save_base sends the post-save signal which causes something called _rename_resize_image in non-Django code to be called, it calls save() on the instance again, and we wind up back in save_base, sending the post-save signal which causes _rename_resize_image to call save() on the instance again, etc. The infinite recursion seems to be caused by your post-save signal handler. What's in there? Seems it needs to be smarter about what it's doing and not continue to try to re-save something it's already been called to fix up. Karen --~--~---------~--~----~------------~-------~--~----~ 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 django-users+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/django-users?hl=en -~----------~----~----~----~------~----~------~--~---
