blocks|key|3100059|text|你是对的，，遵循官方的方式是一个正确的方式，因为创建的视频教程或第三方博客可能会引用旧版本的django，这种方式现在已经被弃用了。|type|unstyled|depth|inlineStyleRanges|offset|length|style|BOLD|entityRanges|data|3100060|祝你一开始就好运！|3100061|entityMap^0|0|5|0|0^^$0|@$1|2|3|4|5|6|7|J|8|@$9|K|A|L|B|C]]|D|@]|E|$]]|$1|F|3|G|5|6|7|M|8|@]|D|@]|E|$]]|$1|H|3|-4|5|6|7|N|8|@]|D|@]|E|$]]]|I|$]]

You are right, following official way is a proper way, since the created video tutorials or third party blogs may refer to the older version of the django and such way is deprecated now.

Good luck in your beginnings!

blocks|key|784186|text|polls.apps.PollsConfig是一种更新、更明确的方式，它更好地允许同一应用程序的多种配置。|type|unstyled|depth|inlineStyleRanges|offset|length|style|CODE|entityRanges|data|784187|polls工作的原因是polls/__init__.py可能有一个|784188|default_app_config+=+'polls.apps.PollsConfig'|code-block|syntax|javascript|784189|线路。|784190|entityMap^0|0|M|0|0|5|B|H|0|0|0^^$0|@$1|2|3|4|5|6|7|Q|8|@$9|R|A|S|B|C]]|D|@]|E|$]]|$1|F|3|G|5|6|7|T|8|@$9|U|A|V|B|C]|$9|W|A|X|B|C]]|D|@]|E|$]]|$1|H|3|I|5|J|7|Y|8|@]|D|@]|E|$K|L]]|$1|M|3|N|5|6|7|Z|8|@]|D|@]|E|$]]|$1|O|3|-4|5|6|7|10|8|@]|D|@]|E|$]]]|P|$]]

The <code>polls.apps.PollsConfig</code> is the newer, more explicit way, and it better allows multiple configurations of the same app.

The reason why <code>polls</code> works is that <code>polls/__init__.py</code> likely has a 

<pre><code>default_app_config = 'polls.apps.PollsConfig'
</code></pre>

line.

blocks|key|4567819|text|你必须激活你的模型，Django需要知道你已经安装了你的应用程序。因此在settings.py中，您需要在INSTALLED_APPS主题中添加'polls.apps.PollsConfig‘，因为在您的app.py文件中，您可能已经定义了一个类PollsConfig：|type|unstyled|depth|inlineStyleRanges|entityRanges|data|4567820|在settings.py中|4567821|INSTALLED_APPS+=+[
++'polls.apps.PollsConfig,
++'django.contrib.admin',
++'<other+app...>',
]|code-block|syntax|javascript|4567822|在apps.py中|4567823|class+PollsConfig(AppConfig)
++++name+=+'polls'|4567824|entityMap^0|0|0|0|0|0^^$0|@$1|2|3|4|5|6|7|O|8|@]|9|@]|A|$]]|$1|B|3|C|5|6|7|P|8|@]|9|@]|A|$]]|$1|D|3|E|5|F|7|Q|8|@]|9|@]|A|$G|H]]|$1|I|3|J|5|6|7|R|8|@]|9|@]|A|$]]|$1|K|3|L|5|F|7|S|8|@]|9|@]|A|$G|H]]|$1|M|3|-4|5|6|7|T|8|@]|9|@]|A|$]]]|N|$]]

You have to activate your model, and Django needs to know that you have your app installed.
So in settings.py you need to add 'polls.apps.PollsConfig' in INSTALLED_APPS topic because in your app.py file you have likely defined a class PollsConfig:

In settings.py

<pre><code>INSTALLED_APPS = [
 'polls.apps.PollsConfig,
 'django.contrib.admin',
 '&lt;other app...&gt;',
]
</code></pre>

In apps.py

<pre><code>class PollsConfig(AppConfig)
 name = 'polls'
</code></pre>

blocks|key|993614|text|在INSTALLED_APPS中，用户可以指定这个django项目应用程序中使用的所有应用程序。|type|unstyled|depth|inlineStyleRanges|offset|length|style|CODE|BOLD|entityRanges|data|993615|但是，您可以在一个项目中创建多个应用程序。默认情况下，这将导致根项目目录中有单独的目录名称。|993616|由于所有应用程序都在根项目目录中-这允许在INSTALLED_APPS中仅指定(它们的)目录名。|993617|另一方面，我们可以指定项目子应用程序AppConfig的完整路径，而不依赖于自动发现/子应用程序位于根项目目录等。|993618|993619|在一个项目中多个应用程序？|993620|是的，一个项目的多个应用程序通常与该特定项目紧密耦合，不能在该项目之外使用。|993621|主要思想是separation+of+concerns+-将逻辑分成单独的部分，每个部分负责项目应用程序的某些部分。|993622|当你的应用程序开始增长时，更多不同的逻辑被添加到它中，models.py+/+views.py+/+forms.py等开始增长，使得阅读和理解整个的项目结构变得困难。|993623|即使是在小项目中，将分成子应用在组织方面也是非常有帮助的。|993624|如何组织你的django应用程序有不同的风格，比如子应用程序目录应该放在哪里(即根目录，或者在带有项目名称的子目录中)，应用程序和设置目录可以不在根项目目录中。在这种情况下，能够直接指定到AppConfig+class的路径是很好的，而且也是更显式的，比隐式更好。|993625|993626|default_app_config主要用于发布到pypi的可重用应用程序-旨在供其他人分发和使用的应用程序。这只允许在INSTALLED_APPS中添加他们的名字，而不是添加到他们的AppConfig的完整路径。|993627|除非您知道自己需要它，否则不应该在项目中使用它。|993628|entityMap|0|LINK|mutability|MUTABLE|url|https://en.wikipedia.org/wiki/Separation_of_concerns|1|https://pypi.org/^0|1|E|P|C|0|0|0|0|0|6|7|0|0|5|M|0|0|R|9|13|8|1E|8|1S|9|0|A|8|0|2M|F|3E|3|3I|3|0|0|0|I|1O|E|P|4|1|0|0^^$0|@$1|2|3|4|5|6|7|1E|8|@$9|1F|A|1G|B|C]|$9|1H|A|1I|B|D]]|E|@]|F|$]]|$1|G|3|H|5|6|7|1J|8|@]|E|@]|F|$]]|$1|I|3|J|5|6|7|1K|8|@]|E|@]|F|$]]|$1|K|3|L|5|6|7|1L|8|@]|E|@]|F|$]]|$1|M|3|-4|5|6|7|1M|8|@]|E|@]|F|$]]|$1|N|3|O|5|6|7|1N|8|@$9|1O|A|1P|B|D]]|E|@]|F|$]]|$1|P|3|Q|5|6|7|1Q|8|@]|E|@]|F|$]]|$1|R|3|S|5|6|7|1R|8|@]|E|@$9|1S|A|1T|1|1U]]|F|$]]|$1|T|3|U|5|6|7|1V|8|@$9|1W|A|1X|B|C]|$9|1Y|A|1Z|B|C]|$9|20|A|21|B|C]|$9|22|A|23|B|D]]|E|@]|F|$]]|$1|V|3|W|5|6|7|24|8|@$9|25|A|26|B|D]]|E|@]|F|$]]|$1|X|3|Y|5|6|7|27|8|@$9|28|A|29|B|C]|$9|2A|A|2B|B|D]|$9|2C|A|2D|B|D]]|E|@]|F|$]]|$1|Z|3|-4|5|6|7|2E|8|@]|E|@]|F|$]]|$1|10|3|11|5|6|7|2F|8|@$9|2G|A|2H|B|C]|$9|2I|A|2J|B|C]]|E|@$9|2K|A|2L|1|2M]]|F|$]]|$1|12|3|13|5|6|7|2N|8|@]|E|@]|F|$]]|$1|14|3|-4|5|6|7|2O|8|@]|E|@]|F|$]]]|15|$16|$5|17|18|19|F|$1A|1B]]|1C|$5|17|18|19|F|$1A|1D]]]]

In <code>INSTALLED_APPS</code> one can specify all apps used in this django project app.

However, you can create multiple apps in one project. By default this would result in separate directories name in root project directory.

As all apps are in root project directory - this allows to specify only (their) directory name in INSTALLED_APPS.

On the other hand, we can specify full path to project sub-app AppConfig, not relying on auto-discovering / that sub-app is located in root project directory etc.

<hr>

Multiple apps in one project?

Yes, multiple apps of one project are usually tightly coupled to this specific project and cannot be used outside of it.

The main idea is <a href="https://en.wikipedia.org/wiki/Separation_of_concerns" rel="nofollow noreferrer">separation of concerns</a> - to split the logic into separate sections, each responsible for some part of project app.

When your app starts growing, more different logic is being added to it, <code>models.py</code> / <code>views.py</code> / <code>forms.py</code> etc starts growing, making it difficult to read and understand project structure as a whole.

Even in small project - separating into sub-apps may be very helpful in terms of organizing things.

There are different styles of how to organize your django app, like where should sub-apps directories be located (i.e. in root directory, or in sub-directory with project name), and apps and settings directories can be located not in root project directory. In such cases being able to specify path directly to <code>AppConfig class</code> is nice and also more explicit, which is better than implicit.

<hr>

<code>default_app_config</code> is mostly used in reusable apps - apps intended to be distributed and used by other people - published to <a href="https://pypi.org/" rel="nofollow noreferrer">pypi</a>. This allows just add their name in <code>INSTALLED_APPS</code>, not full path to their AppConfig.

You should not use it in your project unless you know that you need it.

In every youtube tutorial I'v seen people simply add "app_name" to INSTALLED_APPS list.
Yesterday I started Official Django Tutorial and they suggest "app_name.apps.App_nameConf" notations. 
Im guessing official way is a better way and it's not hard to memorize additional syntax, I just wanna be sure. Because stuff works ether way.
Please give me a simple, easy to understand answer so even I could get it. Thanks!

Django INSTALLED_APPS 'polls' vs 'polls.apps.PollsConfig'

翻译质量差，导致语言生硬或混乱。

没有提供实际的解决方法或示例。

解答不清晰，无法理解或解决问题。

页面排版不美观，阅读体验差。

文章

问答

视频

学习中心

腾讯云实验室

直播

竞赛

腾讯云代码分析专区

腾讯iOA零信任安全管理系统专区

腾讯云架构师技术同盟交流圈

腾讯云数据库专区

腾讯云顾问专区

腾讯云原生专区

腾讯混元专区

腾讯云TCE专区

腾讯云Lighthouse专区

腾讯云HAI专区

腾讯云Edgeone专区

腾讯云存储专区

腾讯云智能专区

腾讯轻联专区 

腾讯云开发专区

TAPD专区

腾讯轻量云游戏服专区

腾讯云最具价值专家

腾讯云架构师技术同盟

腾讯云创作之星

腾讯云开发者先锋

腾讯云代码助手

云原生构建

TAPD 敏捷项目管理

Cloud Studio

SDK中心

API中心

命令行工具

涵盖代码开发、场景应用、自动测试全流程，助你从零构建专属AI助手

一站式MCP教程库，解锁AI应用新玩法

在我见过的每个youtube教程中，人们都会简单地在INSTALLED_APPS列表中添加"app_name“。昨天我开始了官方的Django教程，他们建议使用"app_name.apps.App_nameConf“符号。我猜官方的方式是更好的方式，而且记住额外的语法并不难，我只是想确认一下。因为这些东西都是用来工作的...

问Django INSTALLED_APPS 'polls‘vs 'polls.apps.PollsConfig’
EN

Stack Overflow用户

社区

活动

圈层

关于

腾讯云开发者

热门产品

热门推荐

更多推荐

问Django INSTALLED_APPS 'polls‘vs 'polls.apps.PollsConfig’EN