On Tue, Jun 1, 2010 at 3:02 PM, Gregor Müllegger <gre...@muellegger.de> wrote: > My proposal would go into the direction of pulling the autodiscover > function out of the django.contrib.admin module and putting it > somewhere in the core. Since the admin needs some special > functionality on errors while loading an admin.py module from an app, > I would suggest a Autodiscover class that provides some hooks to be > better customizable. > > Something like: <snip>
I like this idea better then mine provided the startup.py proposal goes forward. I very much dislike having autodiscover stuff being loaded in urls.py as a hack to get an app bootstrapped and part of what I am trying to solve is the need for app consumers (End Developers) to bootstrap your app in urls.py. I figured a setting was slightly more explicit then the bit of magic that would go on by having your own autodiscover sub-class being initiated in startup.py (I really think that should be named bootstrap.py but I digress). Even with the setting there is nothing preventing you from adding your module to the autodiscover setting when you call your management command, but as I said I like the class approach provided a application bootstrap system is provided. If the class based approach is chosen then I think it should love in django.utils.autodiscover as it is something the application developer must subclass if they want to use it, and if it is in core I would expect it to be something used internally and only to be tinkered with by advanced users. -- You received this message because you are subscribed to the Google Groups "Django developers" group. To post to this group, send email to django-develop...@googlegroups.com. To unsubscribe from this group, send email to django-developers+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/django-developers?hl=en.
