Check the output of:

import sys
print sys.modules['admin']

--
Valts


On Tue, Jan 6, 2009 at 20:06, bongo <j...@jdiligence.com> wrote:

>
>
> > In your application directory, the one created by manage.py startapp,
> same
> > as where models.py is.
>
> Thanks.
>
> Thats what I thought I should put it. This is getting weirder though.
> Even though I got autodiscover working it still couldn't find it. I
> then decided to go with the manual method of subclassing the admin app
> and manually wiring it in according to this blog.
>
>
> http://oebfare.com/blog/2008/jul/20/newforms-admin-migration-and-screencast/
>
> It still didn't work but now with an import name error.
>
> Its seems that when I renamed the module from admin.py to
> adrem_admin.py it worked without an import error!
>
> This is crazy but it simply didn't like the module being called
> admin.py!! What is going on? A naming conflict with something in my
> python installation?  I assume it was trying to load the site
> attribute from another module called admin somewhere.. ouch! How can I
> find out what it was really finding?
>
> This has been driving me crazy for days. I now have a manual
> workaround but it means the autodiscover will never work for me..  I
> need to eliminate the real problem if I am ever to use autodiscover.
>
> >
>

--~--~---------~--~----~------------~-------~--~----~
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
-~----------~----~----~----~------~----~------~--~---

Reply via email to