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 models. There is some magic, I'm not sure if it's in AppCache or in the model metaclass, which inspects the import path in which the model class is located and uses it to identify the model class. That means, if you just import another application's models, they will still be recoginzed as belonging to the original application. Michal
signature.asc
Description: Digital signature
