On Oct 7, 10:28 pm, Brent Hagany <[EMAIL PROTECTED]> wrote:
> My apologies if this has been brought up before on this group - my
> searching did not turn up anything, but my search skills are
> notoriously suspect.
>
> I have been reorganizing my code so that it does not depend on the
> project (mostly with success) after watching James Bennet's talk at
> Djangocon about reusable apps. I've chosen to follow the model James
> talks about with respect to Ellington - that is, I have a bunch of
> interdependent apps that are all under the umbrella of one python
> module. Right now, I actually have one umbrella "app", with a bunch
> of proper apps underneath it, so that I only have to put the umbrella
> module in INSTALLED_APPS, rather than each sub-app. I'm not quite
> sure if that's the best way to do this, but more on that in a bit.
This can't be working as you describe it, unless you're doing some
other magic you aren't telling us about to get your models loaded.
The same problem you're having with tests you should be having with
models as well; Django will look for your models in umbrella.models,
not umbrella.app.models, because you just have "umbrella" in
INSTALLED_APPS.
The solution to both problems is to include "umbrella.*" in
INSTALLED_APPS. This will include every app inside the umbrella
package, without you having to list them all separately.
Carl
--~--~---------~--~----~------------~-------~--~----~
You received this message because you are subscribed to the Google Groups
"Django users" 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-users?hl=en
-~----------~----~----~----~------~----~------~--~---