I think you're seeing the same problem I was when I submitted ticket #5505 ( http://code.djangoproject.com/ticket/5505 ). I guess the problem isn't limited to self-referential foreignkeys though, like I originally thought.
The patches db-models-fields-init.patch and newforms-forms.patch fix the problem... for me at least. Like malcom said in his comment though, putting a __deepcopy__ method on Field is probably a bit much.. it might be able to go on just the related objects. Anyway, this patch is at most a temporary measure.. there's definitely more that needs to be worked out with it. Dan On Sep 18, 8:47 am, kan <[EMAIL PROTECTED]> wrote: > Ok Thank you andy > > I did scour through old messages for a other reports of this problem > but did not find it earlier. Thank for the link. > > regards, > suresh. --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Django developers" 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-developers?hl=en -~----------~----~----~----~------~----~------~--~---
