On Sun, Oct 11, 2009 at 6:19 AM, Hanne Moa <hanne....@gmail.com> wrote: > > On Sat, Oct 10, 2009 at 13:51, Russell Keith-Magee > <freakboy3...@gmail.com> wrote: >> Looking at #3591 in particular - another big part of the problem is >> that the ticket tries to solve a theoretical problem that, in >> practice, doesn't really exist - that of namespace collisions in >> applications. > > That's funny, has happended three times to me this far. Not to mention > clashes with globally installed weirdo python libraries I didn't even > know existed before django broke. And it is quite the struggle to > figure out what is actually wrong when this happens. Relative imports > identical to absolute imports are Evil(tm). (Good incentive to always > use virtualenv everywhere though.)
If I may ask - which apps (or app names) caused the collision? Off the top of my head, I can't think of any especially mainstream application that share a package name. In my experience, the fact that having a unique name makes it easier to get Google juice has been enough to keep the namespace clean. Yours, Russ Magee %-) --~--~---------~--~----~------------~-------~--~----~ 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 django-developers+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/django-developers?hl=en -~----------~----~----~----~------~----~------~--~---
