Re: "Project" vs "App"

I'm not sure about saying that a project is a "container for apps", and that a project contains "only" settings and "no database models". At a basic level, a "project" can be just a settings module, but it may include other things. Apps that are sub-packages within a project are generally not

Re: "Project" vs "App"

Hello Thomas, Thanks for bringing this up. There’s definitely some room for improving the documentation — I know because I wrote it. In terms of organization, I’d rather discuss how each topic (settings, models, etc.) relates to projects and apps than talk first about projects, then about

Re: "Project" vs "App"

Without the part of sitecustomize agree with the other parts. + there should be distinction between projects app and install apps Reagards On Thursday, November 19, 2015 at 3:54:40 PM UTC+6, guettli wrote: > > I created a ticket to find a better definition of "Project" vs "App" > >

Re: "Project" vs "App"

So it seems a sitecustomize.py is something internal to your company, and you are proposing to document this for Django in general. So that shouldn't be in there, right? Also, although circular dependencies are probably a sign of a less than perfect design, reality isn't perfect and they

Re: "Project" vs "App"

Am Donnerstag, 19. November 2015 15:12:16 UTC+1 schrieb Collin Anderson: > > What's a sitecustomize.py? :) > This module is automatically imported during initialization if the interpreter. We use it to: - sort sys.path. - monkey patching. During the Update from Django 1.6 to 1.7 we added

Re: "Project" vs "App"

What's a sitecustomize.py? :) I think apps _can_/_may_ be reusable. I have plenty of non-reusable apps. Why should they be reusable? I think apps _should_ not depend on a project. On Thu, Nov 19, 2015 at 4:54 AM, guettli wrote: > I created a ticket to find a