On Apr 11, 11:47 am, mrts <[EMAIL PROTECTED]> wrote: > As double imports should be considered harmful, I'd rather see a > better warning there, in the lines of ""The model Foo is already > registered. This can be caused by a double import, see docs/bar.txt > for ways to avoid it."
Just wondering: why exactly should double imports be "considered harmful"? If the framework detects them and silently ensures that Bad Things Don't Happen, then they aren't harmful, and it's one less finicky little detail to bog one down hunting all over for the source of the problem. --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
