How do “apps” work from django's point of view?











up vote
1
down vote

favorite
1












First of all, the question is technical, not conceptual.



The docs mention, in various places, that you are supposed to put in INSTALLED_APPS the root module of your app. However, what is that module supposed to contain?



Most of the files created by startapp myapp are just there by convention. For example urls, views, admin files are imported from other modules by fully qualified name, and could really be anywhere, so they are just conventions. The only thing that seems to be "hard-coded" in the django logic is the models.py.



So, from the INSTALLED_APPS point of view, does an app consist solely of its models.py? Or is there something else I'm missing? And does the documentation explicitly state this anywhere?






python django







share|improve this question


















  • 1




    I'm no expert in the Django internals, but does this page have the information you want? docs.djangoproject.com/en/2.1/ref/applications. In particular: It is important to understand that a Django application is just a set of code that interacts with various parts of the framework. There’s no such thing as an Application object. However, there’s a few places where Django needs to interact with installed applications, mainly for configuration and also for introspection. That’s why the application registry maintains metadata in an AppConfig instance for each installed application.
    – Robin Zigmond
    Nov 9 at 15:12










  • @RobinZigmond: thanks. the problem is what exactly configuration and retrospection includes. I can't find it anywhere in the docs. The sentence following, seems to enforce my suspicions that only models matter: There’s no restriction that a project package can’t also be considered an application and have models, etc. (which would require adding it to INSTALLED_APPS).
    – blue_note
    Nov 9 at 15:21















up vote
1
down vote

favorite
1












First of all, the question is technical, not conceptual.



The docs mention, in various places, that you are supposed to put in INSTALLED_APPS the root module of your app. However, what is that module supposed to contain?



Most of the files created by startapp myapp are just there by convention. For example urls, views, admin files are imported from other modules by fully qualified name, and could really be anywhere, so they are just conventions. The only thing that seems to be "hard-coded" in the django logic is the models.py.



So, from the INSTALLED_APPS point of view, does an app consist solely of its models.py? Or is there something else I'm missing? And does the documentation explicitly state this anywhere?






python django







share|improve this question


















  • 1




    I'm no expert in the Django internals, but does this page have the information you want? docs.djangoproject.com/en/2.1/ref/applications. In particular: It is important to understand that a Django application is just a set of code that interacts with various parts of the framework. There’s no such thing as an Application object. However, there’s a few places where Django needs to interact with installed applications, mainly for configuration and also for introspection. That’s why the application registry maintains metadata in an AppConfig instance for each installed application.
    – Robin Zigmond
    Nov 9 at 15:12










  • @RobinZigmond: thanks. the problem is what exactly configuration and retrospection includes. I can't find it anywhere in the docs. The sentence following, seems to enforce my suspicions that only models matter: There’s no restriction that a project package can’t also be considered an application and have models, etc. (which would require adding it to INSTALLED_APPS).
    – blue_note
    Nov 9 at 15:21













up vote
1
down vote

favorite
1









up vote
1
down vote

favorite
1






1





First of all, the question is technical, not conceptual.



The docs mention, in various places, that you are supposed to put in INSTALLED_APPS the root module of your app. However, what is that module supposed to contain?



Most of the files created by startapp myapp are just there by convention. For example urls, views, admin files are imported from other modules by fully qualified name, and could really be anywhere, so they are just conventions. The only thing that seems to be "hard-coded" in the django logic is the models.py.



So, from the INSTALLED_APPS point of view, does an app consist solely of its models.py? Or is there something else I'm missing? And does the documentation explicitly state this anywhere?






python django







share|improve this question













First of all, the question is technical, not conceptual.



The docs mention, in various places, that you are supposed to put in INSTALLED_APPS the root module of your app. However, what is that module supposed to contain?



Most of the files created by startapp myapp are just there by convention. For example urls, views, admin files are imported from other modules by fully qualified name, and could really be anywhere, so they are just conventions. The only thing that seems to be "hard-coded" in the django logic is the models.py.



So, from the INSTALLED_APPS point of view, does an app consist solely of its models.py? Or is there something else I'm missing? And does the documentation explicitly state this anywhere?






python django




python django






share|improve this question













share|improve this question











share|improve this question




share|improve this question










asked Nov 9 at 15:00









blue_note

10.7k31831




10.7k31831








  • 1




    I'm no expert in the Django internals, but does this page have the information you want? docs.djangoproject.com/en/2.1/ref/applications. In particular: It is important to understand that a Django application is just a set of code that interacts with various parts of the framework. There’s no such thing as an Application object. However, there’s a few places where Django needs to interact with installed applications, mainly for configuration and also for introspection. That’s why the application registry maintains metadata in an AppConfig instance for each installed application.
    – Robin Zigmond
    Nov 9 at 15:12










  • @RobinZigmond: thanks. the problem is what exactly configuration and retrospection includes. I can't find it anywhere in the docs. The sentence following, seems to enforce my suspicions that only models matter: There’s no restriction that a project package can’t also be considered an application and have models, etc. (which would require adding it to INSTALLED_APPS).
    – blue_note
    Nov 9 at 15:21














  • 1




    I'm no expert in the Django internals, but does this page have the information you want? docs.djangoproject.com/en/2.1/ref/applications. In particular: It is important to understand that a Django application is just a set of code that interacts with various parts of the framework. There’s no such thing as an Application object. However, there’s a few places where Django needs to interact with installed applications, mainly for configuration and also for introspection. That’s why the application registry maintains metadata in an AppConfig instance for each installed application.
    – Robin Zigmond
    Nov 9 at 15:12










  • @RobinZigmond: thanks. the problem is what exactly configuration and retrospection includes. I can't find it anywhere in the docs. The sentence following, seems to enforce my suspicions that only models matter: There’s no restriction that a project package can’t also be considered an application and have models, etc. (which would require adding it to INSTALLED_APPS).
    – blue_note
    Nov 9 at 15:21








1




1




I'm no expert in the Django internals, but does this page have the information you want? docs.djangoproject.com/en/2.1/ref/applications. In particular: It is important to understand that a Django application is just a set of code that interacts with various parts of the framework. There’s no such thing as an Application object. However, there’s a few places where Django needs to interact with installed applications, mainly for configuration and also for introspection. That’s why the application registry maintains metadata in an AppConfig instance for each installed application.
– Robin Zigmond
Nov 9 at 15:12




I'm no expert in the Django internals, but does this page have the information you want? docs.djangoproject.com/en/2.1/ref/applications. In particular: It is important to understand that a Django application is just a set of code that interacts with various parts of the framework. There’s no such thing as an Application object. However, there’s a few places where Django needs to interact with installed applications, mainly for configuration and also for introspection. That’s why the application registry maintains metadata in an AppConfig instance for each installed application.
– Robin Zigmond
Nov 9 at 15:12












@RobinZigmond: thanks. the problem is what exactly configuration and retrospection includes. I can't find it anywhere in the docs. The sentence following, seems to enforce my suspicions that only models matter: There’s no restriction that a project package can’t also be considered an application and have models, etc. (which would require adding it to INSTALLED_APPS).
– blue_note
Nov 9 at 15:21




@RobinZigmond: thanks. the problem is what exactly configuration and retrospection includes. I can't find it anywhere in the docs. The sentence following, seems to enforce my suspicions that only models matter: There’s no restriction that a project package can’t also be considered an application and have models, etc. (which would require adding it to INSTALLED_APPS).
– blue_note
Nov 9 at 15:21












1 Answer
1






active

oldest

votes

















up vote
0
down vote














Thanks to @RobinZigmond for pointing me to the correct part of the docs.




It seems that indeed, everything is a convention, with the exception of models submodule. The description of the initialization process states that for each app in INSTALLED_APPS




  1. the module myapp is imported. models are not ready yet.

  2. the models submodule if myapp is imported. you must import of define your models in models.py or models/__init__.py

  3. sets the corresponding ready flag to True in the application registry






share|improve this answer





















    Your Answer






    StackExchange.ifUsing("editor", function () {
    StackExchange.using("externalEditor", function () {
    StackExchange.using("snippets", function () {
    StackExchange.snippets.init();
    });
    });
    }, "code-snippets");

    StackExchange.ready(function() {
    var channelOptions = {
    tags: "".split(" "),
    id: "1"
    };
    initTagRenderer("".split(" "), "".split(" "), channelOptions);

    StackExchange.using("externalEditor", function() {
    // Have to fire editor after snippets, if snippets enabled
    if (StackExchange.settings.snippets.snippetsEnabled) {
    StackExchange.using("snippets", function() {
    createEditor();
    });
    }
    else {
    createEditor();
    }
    });

    function createEditor() {
    StackExchange.prepareEditor({
    heartbeatType: 'answer',
    convertImagesToLinks: true,
    noModals: true,
    showLowRepImageUploadWarning: true,
    reputationToPostImages: 10,
    bindNavPrevention: true,
    postfix: "",
    imageUploader: {
    brandingHtml: "Powered by u003ca class="icon-imgur-white" href="https://imgur.com/"u003eu003c/au003e",
    contentPolicyHtml: "User contributions licensed under u003ca href="https://creativecommons.org/licenses/by-sa/3.0/"u003ecc by-sa 3.0 with attribution requiredu003c/au003e u003ca href="https://stackoverflow.com/legal/content-policy"u003e(content policy)u003c/au003e",
    allowUrls: true
    },
    onDemand: true,
    discardSelector: ".discard-answer"
    ,immediatelyShowMarkdownHelp:true
    });


    }
    });














     

    draft saved


    draft discarded


















    StackExchange.ready(
    function () {
    StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fstackoverflow.com%2fquestions%2f53228182%2fhow-do-apps-work-from-djangos-point-of-view%23new-answer', 'question_page');
    }
    );

    Post as a guest















    Required, but never shown

























    1 Answer
    1






    active

    oldest

    votes








    1 Answer
    1






    active

    oldest

    votes









    active

    oldest

    votes






    active

    oldest

    votes








    up vote
    0
    down vote














    Thanks to @RobinZigmond for pointing me to the correct part of the docs.




    It seems that indeed, everything is a convention, with the exception of models submodule. The description of the initialization process states that for each app in INSTALLED_APPS




    1. the module myapp is imported. models are not ready yet.

    2. the models submodule if myapp is imported. you must import of define your models in models.py or models/__init__.py

    3. sets the corresponding ready flag to True in the application registry






    share|improve this answer

























      up vote
      0
      down vote














      Thanks to @RobinZigmond for pointing me to the correct part of the docs.




      It seems that indeed, everything is a convention, with the exception of models submodule. The description of the initialization process states that for each app in INSTALLED_APPS




      1. the module myapp is imported. models are not ready yet.

      2. the models submodule if myapp is imported. you must import of define your models in models.py or models/__init__.py

      3. sets the corresponding ready flag to True in the application registry






      share|improve this answer























        up vote
        0
        down vote










        up vote
        0
        down vote










        Thanks to @RobinZigmond for pointing me to the correct part of the docs.




        It seems that indeed, everything is a convention, with the exception of models submodule. The description of the initialization process states that for each app in INSTALLED_APPS




        1. the module myapp is imported. models are not ready yet.

        2. the models submodule if myapp is imported. you must import of define your models in models.py or models/__init__.py

        3. sets the corresponding ready flag to True in the application registry






        share|improve this answer













        Thanks to @RobinZigmond for pointing me to the correct part of the docs.




        It seems that indeed, everything is a convention, with the exception of models submodule. The description of the initialization process states that for each app in INSTALLED_APPS




        1. the module myapp is imported. models are not ready yet.

        2. the models submodule if myapp is imported. you must import of define your models in models.py or models/__init__.py

        3. sets the corresponding ready flag to True in the application registry







        share|improve this answer












        share|improve this answer



        share|improve this answer










        answered Nov 9 at 15:44









        blue_note

        10.7k31831




        10.7k31831






























             

            draft saved


            draft discarded



















































             


            draft saved


            draft discarded














            StackExchange.ready(
            function () {
            StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fstackoverflow.com%2fquestions%2f53228182%2fhow-do-apps-work-from-djangos-point-of-view%23new-answer', 'question_page');
            }
            );

            Post as a guest















            Required, but never shown





















































            Required, but never shown














            Required, but never shown












            Required, but never shown







            Required, but never shown

































            Required, but never shown














            Required, but never shown












            Required, but never shown







            Required, but never shown







            -

            Popular posts from this blog

            Guess what letter conforming each word

            Image
            6 $begingroup$ This is an entry in the Fortnightly Topic Challenge #41: Short and Sweet. 1 letter only could be mean anything . With an additional letter in front , could be used as medicine component and something you definitely learn or at least heard once. Add another letter in front , you would possibly hear that many times . Add an additional letter in front , you would found an independent country . With an additional letter, in the end , you would found something related to apple . Add another letter in the end , you would found something bad . Hint: Each letter is unique . word knowledge letters chemistry share | improve this question ...
            Read more

            Port of Spain

            Image
            For ports in the country of Spain, see List of ports in Spain. City in City of Port of Spain, Trinidad and Tobago Port of Spain City City of Port of Spain Top to bottom (left to right): Skyline of Port of Spain from Gulf of Paria; National Academy for the Performing Arts, Independence Square, Eric Williams Plaza; MovieTowne, Port of Port of Spain Motto(s):  "We Gather Strength As We Go Along" Port of Spain Coordinates: 10°40′N 61°31′W  /  10.667°N 61.517°W  / 10.667; -61.517 Coordinates: 10°40′N 61°31′W  /  10.667°N 61.517°W  / 10.667; -61.517 Country   Trinidad and Tobago Jurisdiction City of Port of Spain Settled 1560 Incorporated (town) 1853 Incorporated (city) 1914 Government  • Mayor Joel Martinez  • Governing body City Corporation Area [1]  • City 12 km 2 (5 sq mi) Elevation [2] 66 m (217 ft) Population (2011) [1]  • City 37,074  • Rank 3rd  • Density 3,090/km 2 (8,000/sq mi)...
            Read more

            Run scheduled task as local user group (not BUILTIN)

            Image
            0 I am trying to run a scheduled task with User Group (not a single user). This is working fine when I in the field "when running a task, use the following user account:" insert BUILTIN User Group (for example: Administrators or Users). But when I try it with the created Local User Group (example: TestGroup) it is not working. The Users in the TestGroup are the same as in the Administrators group. What could be the problem? Are there some restrictions to the Created User Group compared to BUILTINUsers? scheduled-tasks taskscheduler windowstaskschedule share | improve this question asked Nov 15 '18 at 15:36 Far...
            Read more