Mike Dewhirst wrote:
*I also have a "common" app to contain bits and pieces like utilities ...*
I don't keep these under apps; my project-wide utility-type code (code
without Django Models) sits under a "utils" module (with further namespaces
as needed), at the same level as "apps" This means
On 1/03/2018 4:46 AM, Karol Bujaček wrote:
On 02/22/2018 09:44 AM, Cictani wrote:
Hi,
I'm just beginning developing a new app(s) and I'm wondering when I
need to add a new app. if one app uses models from another app is
that a hint that these two apps are acutally one app or is this still
On 02/22/2018 09:44 AM, Cictani wrote:
Hi,
I'm just beginning developing a new app(s) and I'm wondering when I
need to add a new app. if one app uses models from another app is that
a hint that these two apps are acutally one app or is this still ok in
terms of good design?
Let's say I
Hi Andreas,
My rule of thumb is "does this works without the other?" Do your customer
app works without the booking app? Then they are two different apps, with
the second using the first as dependency.
But, then again, I had some people suggesting this wasn't good enough (for
deployment reasons,
This is an indirect reply --- but I like the book "Two Scoops of Django".
It is a strong explanation of Django best practices. (The "scoops" are
scoops of ice cream in the fictional ice cream store of the examples).
Hope this helps.
On Thursday, February 22, 2018 at 7:22:36 AM UTC-5,
5 matches
Mail list logo
