I have attached a patch to #6776 [1] that solves the AlreadyRegistered [2] problem according to what seemed to be the consensus. Which basically is to throw the AlreadyRegistered exception on registration of a different ModelAdmin that may have been previously registered with a model. I am looking to gather some input. It seems that I have needed to implement this similar to the way the AppCache works, which deals with locking the cache when loading new apps. I am not 100% sure whether I need this or not.
Thoughts? [1]: http://code.djangoproject.com/attachment/ticket/6776/6776_modeladmin_fix.2.diff [2]: http://groups.google.com/group/django-developers/browse_frm/thread/1a40c64e9c952c48/7e3d1967d71e4edc?tvc=1&q=ModelAdmin#7e3d1967d71e4edc Brian Rosner http://oebfare.com --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Django developers" group. To post to this group, send email to django-developers@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-developers?hl=en -~----------~----~----~----~------~----~------~--~---
