Still not working, but I suspect a recent upgrade to Django 1.2.4 might be the cause.
Does anyone know (or have experience) of this kind of error when upgrading? On Jan 12, 9:38 am, Derek <gamesb...@gmail.com> wrote: > Working with Django 1.2.3 > > I had an application that was running well. However, some recent changes > (not to the models themselves) have caused the "Runtime Error: maximum > recursion depth exceeded while calling Python object" to start showing up > everywhere; typically in conjunction with the def __unicode__(self) > function. The only major change I have made recently to the system is the > enabling of flatpages, but i cannot see that this is likely to relate to the > model's __unicode__ functions... > > I realize that this is a very "sloppy" error report, but I am wondering if > anyone else has encountered this type of problem (code for models working > and then suddenly generating numbers of the same type of error) and can give > some general pointers on how to solve this (short of ripping out all the > recent changes)? > > Thanks > Derek -- 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.
