On Tue, May 8, 2012 at 9:33 AM, Alex Ogier <[email protected]> wrote: > My guess is that Django is doing some normalization on the name you are > importing. It does this to prevent double imports, for example importing > 'projectname.appname' and 'appname' which would otherwise be considered > separate modules even if they come from the same source. > > Just a theory, but it explains the behavior you are seeing if you are > importing a different name when you do the native import.
This is correct, but it's generally a bad idea to have overlapping import paths due to this double-import problem. I wrote this wart remover some time ago - it might help spot the problem: https://gist.github.com/857091 -- 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.
