Being new in the Python/Django camp (2 weeks) but doing php for
several years, I find this a very interesting topic and I would like
to extend the question a bit, like "when is an app becoming too big?"
The use case here is when you develop a rather complicated "app" which
need to have quite some
Erik Vorhes wrote:
> There's nothing wrong with parceling out models across different apps.
> And unless you're planning on distributing each app separately, don't
> worry about cross-app dependencies.
>
> In this case, I'd encourage you to--since you'll probably want to do
> more than just book-
On Apr 23, 10:29 pm, Jay <[EMAIL PROTECTED]> wrote:
> In the django docs I see that you can easily make a foreign key by
> referencing the model:
>
> manufacturer = models.ForeignKey('production.Manufacturer')
>
> ...but it feels like maybe stepping outside the "django way."
You can also just i
I was thinking along the same lines-- it's more of a single, big app
than a bunch of portables. And I was worried about models.py becoming
too unwieldy. Thanks a lot!
On Apr 23, 4:38 pm, "Erik Vorhes" <[EMAIL PROTECTED]> wrote:
> There's nothing wrong with parceling out models across different
There's nothing wrong with parceling out models across different apps.
And unless you're planning on distributing each app separately, don't
worry about cross-app dependencies.
In this case, I'd encourage you to--since you'll probably want to do
more than just book-related stuff with your people.
I'm working on a project which for the purposes of this conversation
we could say is about authors writing and sharing books.
My tendency is to want to make an app called "people" and an app
called "books," as these are two different models in my mind. A
person has certain attributes which would
6 matches
Mail list logo
