Re: Why apps have to have unique names? [related with subapps and name collision]

Related thread: https://groups.google.com/d/topic/django-developers/9piN0wRFbLs/discussion -- You received this message because you are subscribed to the Google Groups "Django developers" group. To unsubscribe from this group and stop receiving emails from it, send an email to

Re: Why apps have to have unique names? [related with subapps and name collision]

On Mon, Jun 03, 2013 at 01:04:34PM +0300, Yishai Beeri wrote: > Is this not almost trivial to work around by creating a new module > 'newapp', importing the original app code from it, and then using > 'path.to.newapp' as a new "copy" of the app in INSTALLED_APPS? Not really. At least not for

Re: Why apps have to have unique names? [related with subapps and name collision]

Is this not almost trivial to work around by creating a new module 'newapp', importing the original app code from it, and then using 'path.to.newapp' as a new "copy" of the app in INSTALLED_APPS? Yishai On Mon, 03 Jun 2013 12:24:38 +0300, Aymeric Augustin

Re: Why apps have to have unique names? [related with subapps and name collision]

2013/6/3 Jorge C. Leitão Motivated by that criticism, I want to ask: why apps have to have unique > names? > Hi Jorge, Django assumes that a model can be identified by (app_name, model_name). Long ago — 8 years ago — it didn't seem to be a problem. I'm not sure your

Why apps have to have unique names? [related with subapps and name collision]

Hi. The motivation to this question is that if I want to implement "copies" of an app within an website (for instance, a stackoverflow-like where each app is a Q for its own, but with modifications on templates, urls, etc.), as far as I'm understanding: (1) each "copy" has to change its name,