blocks|key|4388971|text|您是否错过了在设置文件中输入您的应用程序名称？myAppNameConfig是在apps.py中由.manage.py+createapp+myAppName命令生成的默认类。其中myAppName是您的应用程序的名称。|type|unstyled|depth|inlineStyleRanges|offset|length|style|CODE|entityRanges|data|4388972|settings.py|4388973|INSTALLED_APPS+=+[
'myAppName.apps.myAppNameConfig',
'django.contrib.admin',
'django.contrib.auth',
'django.contrib.contenttypes',
'django.contrib.sessions',
'django.contrib.messages',
'django.contrib.staticfiles',
]|code-block|syntax|javascript|4388974|这样，设置文件就会找出您想要为应用程序命名的名称。稍后，您可以通过在apps.py文件中添加以下代码来更改它的外观|4388975|myAppName/apps.py|4388976|class+myAppNameConfig(AppConfig):
++++name+=+'myAppName'
++++verbose_name+=+'A+Much+Better+Name'|4388977|entityMap^0|N|F|1D|U|2I|9|0|0|0|0|0|0^^$0|@$1|2|3|4|5|6|7|U|8|@$9|V|A|W|B|C]|$9|X|A|Y|B|C]|$9|Z|A|10|B|C]]|D|@]|E|$]]|$1|F|3|G|5|6|7|11|8|@]|D|@]|E|$]]|$1|H|3|I|5|J|7|12|8|@]|D|@]|E|$K|L]]|$1|M|3|N|5|6|7|13|8|@]|D|@]|E|$]]|$1|O|3|P|5|6|7|14|8|@]|D|@]|E|$]]|$1|Q|3|R|5|J|7|15|8|@]|D|@]|E|$K|L]]|$1|S|3|-4|5|6|7|16|8|@]|D|@]|E|$]]]|T|$]]

Are you missing putting in your application name into the settings file?
The <code>myAppNameConfig</code> is the default class generated at apps.py by the <code>.manage.py createapp myAppName</code> command. Where <code>myAppName</code> is the name of your app.
settings.py
<pre><code>INSTALLED_APPS = [
'myAppName.apps.myAppNameConfig',
'django.contrib.admin',
'django.contrib.auth',
'django.contrib.contenttypes',
'django.contrib.sessions',
'django.contrib.messages',
'django.contrib.staticfiles',
]
</code></pre>
This way, the settings file finds out what you want to call your application. You can change how it looks later in the apps.py file by adding the following code in
myAppName/apps.py
<pre><code>class myAppNameConfig(AppConfig):
 name = 'myAppName'
 verbose_name = 'A Much Better Name'
</code></pre>

blocks|key|4389391|text|当我试图将我的Django+Rest+Framework应用升级到DRF+3.6.3和Django+1.11.1时，我得到了这个错误。|type|unstyled|depth|inlineStyleRanges|entityRanges|offset|length|data|4389392|对于这种情况下的其他任何人，我找到了我的解决方案in+a+GitHub+issue，即在DRF+settings中取消设置UNAUTHENTICATED_USER设置|style|CODE|4389393|#+webapp/settings.py
...
REST_FRAMEWORK+=+{
++++...
++++'UNAUTHENTICATED_USER':+None
++++...
}|code-block|syntax|javascript|4389394|entityMap|0|LINK|mutability|MUTABLE|url|http://www.django-rest-framework.org/|1|https://github.com/encode/django-rest-framework/issues/3262#issuecomment-147541598|2|http://www.django-rest-framework.org/api-guide/settings/^0|7|L|0|0|1P|K|O|H|1|18|C|2|0|0^^$0|@$1|2|3|4|5|6|7|Y|8|@]|9|@$A|Z|B|10|1|11]]|C|$]]|$1|D|3|E|5|6|7|12|8|@$A|13|B|14|F|G]]|9|@$A|15|B|16|1|17]|$A|18|B|19|1|1A]]|C|$]]|$1|H|3|I|5|J|7|1B|8|@]|9|@]|C|$K|L]]|$1|M|3|-4|5|6|7|1C|8|@]|9|@]|C|$]]]|N|$O|$5|P|Q|R|C|$S|T]]|U|$5|P|Q|R|C|$S|V]]|W|$5|P|Q|R|C|$S|X]]]]

I got this error while trying to upgrade my <a href="http://www.django-rest-framework.org/" rel="nofollow noreferrer">Django Rest Framework</a> app to DRF 3.6.3 and Django 1.11.1.

For anyone else in this situation, I found my solution <a href="https://github.com/encode/django-rest-framework/issues/3262#issuecomment-147541598" rel="nofollow noreferrer">in a GitHub issue</a>, which was to unset the <code>UNAUTHENTICATED_USER</code> setting in the <a href="http://www.django-rest-framework.org/api-guide/settings/" rel="nofollow noreferrer">DRF settings</a>:

<pre><code># webapp/settings.py
...
REST_FRAMEWORK = {
 ...
 'UNAUTHENTICATED_USER': None
 ...
}
</code></pre>

blocks|key|4389418|text|我在使用./manage.py+shell时得到了这个文件，然后意外地从根项目级目录导入了该文件|type|unstyled|depth|inlineStyleRanges|offset|length|style|CODE|entityRanges|data|4389419|#+don't+do+this
from+project.someapp.someModule+import+something_using_a_model
#+do+this
from+someapp.someModule+import+something_using_a_model

something_using_a_model()|code-block|syntax|javascript|4389420|entityMap^0|4|H|0|0^^$0|@$1|2|3|4|5|6|7|M|8|@$9|N|A|O|B|C]]|D|@]|E|$]]|$1|F|3|G|5|H|7|P|8|@]|D|@]|E|$I|J]]|$1|K|3|-4|5|6|7|Q|8|@]|D|@]|E|$]]]|L|$]]

I got this one when I used <code>./manage.py shell</code>
then I accidentally imported from the root project level directory

<pre><code># don't do this
from project.someapp.someModule import something_using_a_model
# do this
from someapp.someModule import something_using_a_model

something_using_a_model()
</code></pre>

blocks|key|4389455|text|在我将SECRET_KEY从环境变量中移到pull，但在运行应用程序时忘记设置它之后，我收到了这个错误。如果你的settings.py中有类似这样的东西|type|unstyled|depth|inlineStyleRanges|offset|length|style|CODE|entityRanges|data|4389456|SECRET_KEY+=+os.getenv('SECRET_KEY')|code-block|syntax|javascript|4389457|然后确保您实际设置的是环境变量。|4389458|entityMap^0|3|A|1K|B|0|0|0^^$0|@$1|2|3|4|5|6|7|O|8|@$9|P|A|Q|B|C]|$9|R|A|S|B|C]]|D|@]|E|$]]|$1|F|3|G|5|H|7|T|8|@]|D|@]|E|$I|J]]|$1|K|3|L|5|6|7|U|8|@]|D|@]|E|$]]|$1|M|3|-4|5|6|7|V|8|@]|D|@]|E|$]]]|N|$]]

I received this error after I moved the <code>SECRET_KEY</code> to pull from an environment variable and forgot to set it when running the application. If you have something like this in your <code>settings.py</code>

<pre><code>SECRET_KEY = os.getenv('SECRET_KEY')
</code></pre>

then make sure you are actually setting the environment variable.

blocks|key|4389488|text|当我尝试为由于git合并而存在格式错误的迁移的单个应用程序生成迁移时，我遇到了这个错误。例如：|type|unstyled|depth|inlineStyleRanges|entityRanges|data|4389489|manage.py+makemigrations+myapp|code-block|syntax|javascript|4389490|当我删除它的迁移，然后运行：|4389491|manage.py+makemigrations|4389492|未出现错误，迁移已成功生成。|4389493|entityMap^0|0|0|0|0|0^^$0|@$1|2|3|4|5|6|7|O|8|@]|9|@]|A|$]]|$1|B|3|C|5|D|7|P|8|@]|9|@]|A|$E|F]]|$1|G|3|H|5|6|7|Q|8|@]|9|@]|A|$]]|$1|I|3|J|5|D|7|R|8|@]|9|@]|A|$E|F]]|$1|K|3|L|5|6|7|S|8|@]|9|@]|A|$]]|$1|M|3|-4|5|6|7|T|8|@]|9|@]|A|$]]]|N|$]]

I ran into this error when I tried generating migrations for a single app which had existing malformed migrations due to a git merge. e.g.

<pre><code>manage.py makemigrations myapp
</code></pre>

When I deleted it's migrations and then ran:

<pre><code>manage.py makemigrations
</code></pre>

the error did not occur and the migrations generated successfully.

blocks|key|4389163|text|我在测试中导入模型时遇到了这个错误，即给定Django项目结构：|type|unstyled|depth|inlineStyleRanges|entityRanges|data|4389164|%7C--+myproject
++++%7C--+manage.py
++++%7C--+myproject
++++%7C--+myapp
++++++++%7C--+models.py++#+defines+model:+MyModel
++++++++%7C--+tests
++++++++++++%7C--+test_models.py|code-block|syntax|javascript|4389165|在test_models.py文件中，我是这样导入MyModel的：|offset|length|style|CODE|4389166|from+models+import+MyModel|4389167|如果以这种方式导入，则问题已修复：|4389168|from+myapp.models+import+MyModel|4389169|希望这能有所帮助！|4389170|PS:也许这有点晚了，但我在我的代码中没有找到如何解决这个问题的答案，我想分享我的解决方案。|4389171|entityMap^0|0|0|1|E|P|7|0|0|0|0|0|0^^$0|@$1|2|3|4|5|6|7|Y|8|@]|9|@]|A|$]]|$1|B|3|C|5|D|7|Z|8|@]|9|@]|A|$E|F]]|$1|G|3|H|5|6|7|10|8|@$I|11|J|12|K|L]|$I|13|J|14|K|L]]|9|@]|A|$]]|$1|M|3|N|5|D|7|15|8|@]|9|@]|A|$E|F]]|$1|O|3|P|5|6|7|16|8|@]|9|@]|A|$]]|$1|Q|3|R|5|D|7|17|8|@]|9|@]|A|$E|F]]|$1|S|3|T|5|6|7|18|8|@]|9|@]|A|$]]|$1|U|3|V|5|6|7|19|8|@]|9|@]|A|$]]|$1|W|3|-4|5|6|7|1A|8|@]|9|@]|A|$]]]|X|$]]

I got this error on importing models in tests, i.e. given this Django project structure:

<pre><code>|-- myproject
 |-- manage.py
 |-- myproject
 |-- myapp
 |-- models.py # defines model: MyModel
 |-- tests
 |-- test_models.py
</code></pre>

in file <code>test_models.py</code> I imported <code>MyModel</code> in this way:

<pre><code>from models import MyModel
</code></pre>

The problem was fixed if it is imported in this way:

<pre><code>from myapp.models import MyModel
</code></pre>

Hope this helps!

PS: Maybe this is a bit late, but I not found in others answers how to solve this problem in my code and I want to share my solution.

blocks|key|4389553|text|我今天收到了这个错误，并在谷歌搜索后出现在这里。现有的答案似乎没有一个与我的情况相关。我唯一需要做的就是从应用程序顶层的__init__.py文件中导入一个模型。我必须使用模型将我的导入移动到函数中。|type|unstyled|depth|inlineStyleRanges|offset|length|style|CODE|entityRanges|data|4389554|Django似乎有一些奇怪的代码，在这么多不同的场景中可能会像这样失败！|4389555|entityMap^0|1O|B|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|$]]

I got this error today and ended up here after googling. None of the existing answers seem relevant to my situation. The only thing I needed to do was to import a model from my <code>__init__.py</code> file in the top level of an app. I had to move my imports into the functions using the model.

Django seems to have some weird code that can fail like this in so many different scenarios!

blocks|key|4389599|text|在我的例子中，当将代码从Django+1.11.11移植到Django+2.2时，我得到了这个错误。我正在定义一个自定义的FileSystemStorage派生类。在Django+1.11.11中，我在models.py中使用了以下代码：|type|unstyled|depth|inlineStyleRanges|entityRanges|data|4389600|from+django.core.files.storage+import+Storage,+DefaultStorage|code-block|syntax|javascript|4389601|在后面的文件中，我有了类定义：|4389602|class+MyFileStorage(FileSystemStorage):|4389603|然而，在Django+2.2中，我需要在导入时显式引用FileSystemStorage类：|offset|length|style|CODE|4389604|from+django.core.files.storage+import+Storage,+DefaultStorage,+FileSystemStorage|4389605|瞧，错误消失了。|4389606|请注意，每个人都报告了Django服务器产生的错误消息的最后一部分。然而，如果你向上滚动，你会在错误的中间找到原因。|4389607|entityMap^0|0|0|0|0|R|H|0|0|0|0^^$0|@$1|2|3|4|5|6|7|Y|8|@]|9|@]|A|$]]|$1|B|3|C|5|D|7|Z|8|@]|9|@]|A|$E|F]]|$1|G|3|H|5|6|7|10|8|@]|9|@]|A|$]]|$1|I|3|J|5|D|7|11|8|@]|9|@]|A|$E|F]]|$1|K|3|L|5|6|7|12|8|@$M|13|N|14|O|P]]|9|@]|A|$]]|$1|Q|3|R|5|D|7|15|8|@]|9|@]|A|$E|F]]|$1|S|3|T|5|6|7|16|8|@]|9|@]|A|$]]|$1|U|3|V|5|6|7|17|8|@]|9|@]|A|$]]|$1|W|3|-4|5|6|7|18|8|@]|9|@]|A|$]]]|X|$]]

In my case I got this error when porting code from Django 1.11.11 to Django 2.2. I was defining a custom FileSystemStorage derived class. In Django 1.11.11 I was having the following line in models.py:

<pre><code>from django.core.files.storage import Storage, DefaultStorage
</code></pre>

and later in the file I had the class definition:

<pre><code>class MyFileStorage(FileSystemStorage):
</code></pre>

However, in Django 2.2 I need to explicitly reference <code>FileSystemStorage</code> class when importing:

<pre><code>from django.core.files.storage import Storage, DefaultStorage, FileSystemStorage
</code></pre>

and voilà!, the error dissapears.

Note, that everyone is reporting the last part of the error message spitted by Django server. However, if you scroll up you will find the reason in the middle of that error mambo-jambo.

blocks|key|4389266|text|在我的例子中，我能够找到一个修复，通过查看其他人的代码，它可能是相同的问题。我只需要在settings.py文件的已安装应用列表中添加'django.contrib.sites‘即可。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|4389267|希望这对某些人有帮助。这是我对编码社区的第一次贡献。|4389268|entityMap^0|0|0^^$0|@$1|2|3|4|5|6|7|F|8|@]|9|@]|A|$]]|$1|B|3|C|5|6|7|G|8|@]|9|@]|A|$]]|$1|D|3|-4|5|6|7|H|8|@]|9|@]|A|$]]]|E|$]]

in my case I was able to find a fix and by looking at the everyone else's code it may be the same issue.. I simply just had to add 'django.contrib.sites' to the list of installed apps in the settings.py file.

hope this helps someone. this is my first contribution to the coding community

blocks|key|4389688|text|我今天尝试运行Django测试时遇到了这个错误，因为我在我的一个文件中使用了简写的from+.models+import+*语法。问题是我的文件结构是这样的：|type|unstyled|depth|inlineStyleRanges|offset|length|style|CODE|entityRanges|data|4389689|++++apps/
++++++myapp/
++++++++models/
++++++++++__init__.py
++++++++++foo.py
++++++++++bar.py|code-block|syntax|javascript|4389690|在models/__init__.py中，我使用简写语法导入模型：|4389691|++++from+.foo+import+*
++++from+.bar+import+*|4389692|在我的应用程序中，我像这样导入模型：|4389693|++++from+myapp.models+import+Foo,+Bar|4389694|这导致在运行./manage.py+test时出现Django+model+doesn't+declare+an+explicit+app_label。|4389695|要解决这个问题，我必须显式地从models/__init__.py中的完整路径导入|4389696|++++from+myapp.models.foo+import+*
++++from+myapp.models.bar+import+*|4389697|解决了这个错误。|4389698|H/t+https://medium.com/@michal.bock/fix-weird-exceptions-when-running-django-tests-f58def71b59a|4389699|entityMap|0|LINK|mutability|MUTABLE|url|https://medium.com/@michal.bock/fix-weird-exceptions-when-running-django-tests-f58def71b59a^0|15|L|0|0|1|I|0|0|0|0|6|G|P|1E|0|F|I|0|0|0|4|2J|0|0^^$0|@$1|2|3|4|5|6|7|1A|8|@$9|1B|A|1C|B|C]]|D|@]|E|$]]|$1|F|3|G|5|H|7|1D|8|@]|D|@]|E|$I|J]]|$1|K|3|L|5|6|7|1E|8|@$9|1F|A|1G|B|C]]|D|@]|E|$]]|$1|M|3|N|5|H|7|1H|8|@]|D|@]|E|$I|J]]|$1|O|3|P|5|6|7|1I|8|@]|D|@]|E|$]]|$1|Q|3|R|5|H|7|1J|8|@]|D|@]|E|$I|J]]|$1|S|3|T|5|6|7|1K|8|@$9|1L|A|1M|B|C]|$9|1N|A|1O|B|C]]|D|@]|E|$]]|$1|U|3|V|5|6|7|1P|8|@$9|1Q|A|1R|B|C]]|D|@]|E|$]]|$1|W|3|X|5|H|7|1S|8|@]|D|@]|E|$I|J]]|$1|Y|3|Z|5|6|7|1T|8|@]|D|@]|E|$]]|$1|10|3|11|5|6|7|1U|8|@]|D|@$9|1V|A|1W|1|1X]]|E|$]]|$1|12|3|-4|5|6|7|1Y|8|@]|D|@]|E|$]]]|13|$14|$5|15|16|17|E|$18|19]]]]

I had this error today trying to run Django tests because I was using the shorthand <code>from .models import *</code> syntax in one of my files. The issue was that I had a file structure like so:

<pre><code> apps/
 myapp/
 models/
 __init__.py
 foo.py
 bar.py
</code></pre>

and in <code>models/__init__.py</code> I was importing my models using the shorthand syntax:

<pre><code> from .foo import *
 from .bar import *
</code></pre>

In my application I was importing models like so:

<pre><code> from myapp.models import Foo, Bar
</code></pre>

This caused the <code>Django model doesn't declare an explicit app_label</code> when running <code>./manage.py test</code>.

To fix the problem, I had to explicitly import from the full path in <code>models/__init__.py</code>:

<pre><code> from myapp.models.foo import *
 from myapp.models.bar import *
</code></pre>

That took care of the error.

H/t <a href="https://medium.com/@michal.bock/fix-weird-exceptions-when-running-django-tests-f58def71b59a" rel="noreferrer">https://medium.com/@michal.bock/fix-weird-exceptions-when-running-django-tests-f58def71b59a</a>

blocks|key|4389364|text|如果你所有的配置都是正确的，那么它可能只是一个导入混乱。注意如何导入有问题的模型。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|4389365|下面的代码将不会在from+.models+import+Business中运行。改用完整导入路径：from+myapp.models+import+Business|offset|length|style|CODE|4389366|entityMap^0|0|9|S|1E|X|0^^$0|@$1|2|3|4|5|6|7|J|8|@]|9|@]|A|$]]|$1|B|3|C|5|6|7|K|8|@$D|L|E|M|F|G]|$D|N|E|O|F|G]]|9|@]|A|$]]|$1|H|3|-4|5|6|7|P|8|@]|9|@]|A|$]]]|I|$]]

If you have got all the config right, it might just be an import mess. keep an eye on how you are importing the offending model.

The following won't work <code>from .models import Business</code>. Use full import path instead: <code>from myapp.models import Business</code>

blocks|key|4389771|text|O…M…G我也遇到了这个错误，我花了几乎2天的时间来解决它，现在我终于设法解决了它。Honestly...the错误与问题无关。在我的例子中，这是一个简单的语法问题。我试图运行一个独立的python模块，它在django上下文中使用了一些django模型，但模块本身并不是django模型。但是我声明这个类是错误的|type|unstyled|depth|inlineStyleRanges|entityRanges|data|4389772|而不是让|4389773|class+Scrapper:
++++name+=+""
++++main_link=+""
++++...|code-block|syntax|javascript|4389774|我在做|4389775|class+Scrapper(Website):
++++name+=+""
++++main_link=+""
++++...|4389776|这显然是错误的。这条消息太具误导性了，以至于我不由自主地认为这是配置的问题，或者只是错误地使用了django，因为我对它非常陌生。|4389777|我将在这里与一些新手分享这一点，因为我经历了同样愚蠢的事情，希望能解决他们的问题。|4389778|entityMap^0|0|0|0|0|0|0|0^^$0|@$1|2|3|4|5|6|7|S|8|@]|9|@]|A|$]]|$1|B|3|C|5|6|7|T|8|@]|9|@]|A|$]]|$1|D|3|E|5|F|7|U|8|@]|9|@]|A|$G|H]]|$1|I|3|J|5|6|7|V|8|@]|9|@]|A|$]]|$1|K|3|L|5|F|7|W|8|@]|9|@]|A|$G|H]]|$1|M|3|N|5|6|7|X|8|@]|9|@]|A|$]]|$1|O|3|P|5|6|7|Y|8|@]|9|@]|A|$]]|$1|Q|3|-4|5|6|7|Z|8|@]|9|@]|A|$]]]|R|$]]

O...M...G
I was getting this error too and I spent almost 2 days on it and now I finally managed to solve it. Honestly...the error had nothing to do with what the problem was.
In my case it was a simple matter of syntax. I was trying to run a python module standalone that used some django models in a django context, but the module itself wasn't a django model. But I was declaring the class wrong

instead of having

<pre><code>class Scrapper:
 name = ""
 main_link= ""
 ...
</code></pre>

I was doing

<pre><code>class Scrapper(Website):
 name = ""
 main_link= ""
 ...
</code></pre>

which is obviously wrong. The message is so misleading that I couldn't help myself but think it was some issue with configuration or just using django in a wrong way since I'm very new to it. 

I'll share this here for someone newbie as me going through the same silliness can hopefully solve their issue.

blocks|key|4389848|text|在不断遇到这个问题并不断回到这个问题之后，我想我应该分享一下我的问题是什么。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|4389849|所有@Xeberdee都是正确的，所以请遵循它，看看这是否解决了问题，如果不是，这是我的问题：|4389850|在我的apps.py中，这是我拥有的：|4389851|class+AlgoExplainedConfig(AppConfig):
++++name+=+'algo_explained'
++++verbose_name+=+"Explain_Algo"
++++....|code-block|syntax|javascript|4389852|我所做的就是在我的应用程序名称前面添加项目名称，如下所示：|4389853|class+AlgoExplainedConfig(AppConfig):
name+=+'**algorithms_explained**.algo_explained'
verbose_name+=+"Explain_Algo"|4389854|这就解决了我的问题，然后我就可以运行makemigrations和migrate命令了！祝好运|4389855|entityMap^0|0|0|0|0|0|0|0^^$0|@$1|2|3|4|5|6|7|S|8|@]|9|@]|A|$]]|$1|B|3|C|5|6|7|T|8|@]|9|@]|A|$]]|$1|D|3|E|5|6|7|U|8|@]|9|@]|A|$]]|$1|F|3|G|5|H|7|V|8|@]|9|@]|A|$I|J]]|$1|K|3|L|5|6|7|W|8|@]|9|@]|A|$]]|$1|M|3|N|5|H|7|X|8|@]|9|@]|A|$I|J]]|$1|O|3|P|5|6|7|Y|8|@]|9|@]|A|$]]|$1|Q|3|-4|5|6|7|Z|8|@]|9|@]|A|$]]]|R|$]]

After keep on running into this issue and keep on coming back to this question I thought I'd share what my problem was. 

Everything that @Xeberdee is correct so follow that and see if that solves the issue, if not this was my issue: 

In my apps.py this is what I had: 

<pre><code>class AlgoExplainedConfig(AppConfig):
 name = 'algo_explained'
 verbose_name = "Explain_Algo"
 ....
</code></pre>

And all I did was I added the project name in front of my app name like this:

<pre><code>class AlgoExplainedConfig(AppConfig):
name = '**algorithms_explained**.algo_explained'
verbose_name = "Explain_Algo"
</code></pre>

and that solved my problem and I was able to run the makemigrations and migrate command after that! good luck

blocks|key|4389569|text|对于PyCharm用户:我在使用不“干净”的项目结构时出错。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|4389570|是：|4389571|project_root_directory
└──+src
++++├──+chat
++++│  +├──+migrations
++++│  +└──+templates
++++├──+django_channels
++++└──+templates|code-block|syntax|javascript|4389572|现在：|4389573|project_root_directory
├──+chat
│+++├──+migrations
│+++└──+templates
│+++++++└──+chat
├──+django_channels
└──+templates|4389574|这里有很多很好的解决方案，但我认为，首先，你应该在设置DJANGO_SETTINGS_MODULE变量之前清理你的项目结构或调整PyCharm+Django设置。|offset|length|style|CODE|4389575|希望这能帮助到某个人。干杯。|4389576|entityMap^0|0|0|0|0|0|R|M|0|0^^$0|@$1|2|3|4|5|6|7|W|8|@]|9|@]|A|$]]|$1|B|3|C|5|6|7|X|8|@]|9|@]|A|$]]|$1|D|3|E|5|F|7|Y|8|@]|9|@]|A|$G|H]]|$1|I|3|J|5|6|7|Z|8|@]|9|@]|A|$]]|$1|K|3|L|5|F|7|10|8|@]|9|@]|A|$G|H]]|$1|M|3|N|5|6|7|11|8|@$O|12|P|13|Q|R]]|9|@]|A|$]]|$1|S|3|T|5|6|7|14|8|@]|9|@]|A|$]]|$1|U|3|-4|5|6|7|15|8|@]|9|@]|A|$]]]|V|$]]

For PyCharm users: I had an error using not "clean" project structure.

Was:

<pre><code>project_root_directory
└── src
 ├── chat
 │   ├── migrations
 │   └── templates
 ├── django_channels
 └── templates
</code></pre>

Now:

<pre><code>project_root_directory
├── chat
│ ├── migrations
│ └── templates
│ └── chat
├── django_channels
└── templates
</code></pre>

Here is a lot of good solutions, but I think, first of all, you should clean your project structure or tune PyCharm Django settings before setting <code>DJANGO_SETTINGS_MODULE</code> variables and so on.

Hope it'll help someone. Cheers.

blocks|key|4389994|text|我也有类似的问题，但是我能够通过在我的models类中使用Meta类显式地指定app_label来解决我的问题|type|unstyled|depth|inlineStyleRanges|entityRanges|data|4389995|class+Meta:
++++app_label++=+'name_of_my_app'|code-block|syntax|javascript|4389996|entityMap^0|0|0^^$0|@$1|2|3|4|5|6|7|I|8|@]|9|@]|A|$]]|$1|B|3|C|5|D|7|J|8|@]|9|@]|A|$E|F]]|$1|G|3|-4|5|6|7|K|8|@]|9|@]|A|$]]]|H|$]]

I had a similar issue, but I was able to solve mine by specifying explicitly the app_label using Meta Class in my models class
<pre><code>class Meta:
 app_label = 'name_of_my_app'
</code></pre>

blocks|key|4390028|text|在我的例子中，在没有连接到项目的虚拟环境的情况下尝试运行python+manage.py+runserver时，我得到了这个错误。|type|unstyled|depth|inlineStyleRanges|offset|length|style|CODE|entityRanges|data|4390029|entityMap^0|S|Q|0^^$0|@$1|2|3|4|5|6|7|H|8|@$9|I|A|J|B|C]]|D|@]|E|$]]|$1|F|3|-4|5|6|7|K|8|@]|D|@]|E|$]]]|G|$]]

In my case I was getting this error when trying to run <code>python manage.py runserver</code> when not connected to my project's virtual environment.

blocks|key|4390052|text|还要检查您的迁移是否正常工作|type|unstyled|depth|inlineStyleRanges|entityRanges|data|4390053|Python3+manage.py+makemigrations
Python3+manage.py+migrate|code-block|syntax|javascript|4390054|entityMap^0|0|0^^$0|@$1|2|3|4|5|6|7|I|8|@]|9|@]|A|$]]|$1|B|3|C|5|D|7|J|8|@]|9|@]|A|$E|F]]|$1|G|3|-4|5|6|7|K|8|@]|9|@]|A|$]]]|H|$]]

Check also that your migrations are working correctly
<pre><code>Python3 manage.py makemigrations
Python3 manage.py migrate
</code></pre>

blocks|key|4390102|text|在我的例子中，settings.py中的BASE_DIR有一个问题，这是包的结构：|type|unstyled|depth|inlineStyleRanges|entityRanges|data|4390103|project_root_directory
└──+service_package
++++└──+db_package
++++++++├──+my_django_package
++++++++│+++++++└──+my_django_package
++++++++│+++++++  +├──+settings.py
++++++++│+++++++  +└──+...
++++++++└──+my_django_app
+++++++++++++++├──+migrations
+++++++++++++++├──+models.py
+++++++++++++++└──+...|code-block|syntax|javascript|4390104|当使用以下命令更新settings.py时，它可以正常工作：|4390105|INSTALLED_APPS+=+[
++++'some_django_stuff_here...',
++++'some_django_stuff_here....',
++++...
++++'service_package.db_package.my_django_app'
]|4390106|和指向项目根目录的BASE_DIR|4390107|BASE_DIR+=+Path(__file__).resolve().parent.parent.parent.parent.parent|4390108|在debug中运行django，在registry.py+->+def+get_containing_app_config(self，object_name)中使用断点后，出现了这个问题。|4390109|entityMap^0|0|0|0|0|0|0|0^^$0|@$1|2|3|4|5|6|7|S|8|@]|9|@]|A|$]]|$1|B|3|C|5|D|7|T|8|@]|9|@]|A|$E|F]]|$1|G|3|H|5|6|7|U|8|@]|9|@]|A|$]]|$1|I|3|J|5|D|7|V|8|@]|9|@]|A|$E|F]]|$1|K|3|L|5|6|7|W|8|@]|9|@]|A|$]]|$1|M|3|N|5|D|7|X|8|@]|9|@]|A|$E|F]]|$1|O|3|P|5|6|7|Y|8|@]|9|@]|A|$]]|$1|Q|3|-4|5|6|7|Z|8|@]|9|@]|A|$]]]|R|$]]

In my case, there was an issue with BASE_DIR in settings.py This is the structure of the packages:
<pre><code>project_root_directory
└── service_package
 └── db_package
 ├── my_django_package
 │ └── my_django_package
 │    ├── settings.py
 │    └── ...
 └── my_django_app
 ├── migrations
 ├── models.py
 └── ...
</code></pre>
It worked when updated the settings.py with:
<pre><code>INSTALLED_APPS = [
 'some_django_stuff_here...',
 'some_django_stuff_here....',
 ...
 'service_package.db_package.my_django_app'
]
</code></pre>
And BASE_DIR pointing to the project root
<pre><code>BASE_DIR = Path(__file__).resolve().parent.parent.parent.parent.parent
</code></pre>
Came to this after running django in debug, with breakpoint in registry.py -&gt; def get_containing_app_config(self, object_name)

blocks|key|4390166|text|在我的例子中，我在manage.py+shell中尝试了相同的导入。shell被更新的数据库搞乱了。我的意思是，我忘记在更新数据库后重启我的shell。|type|unstyled|depth|inlineStyleRanges|offset|length|style|CODE|entityRanges|data|4390167|为了解决这个问题，我必须通过以下命令停止shell：|4390168|>>>+exit()|code-block|syntax|javascript|4390169|然后通过以下命令重启shell：|4390170|$+python3+manage.py+shell|4390171|希望这能对像我这样的人有所帮助。|4390172|entityMap^0|9|F|0|0|0|0|0|0^^$0|@$1|2|3|4|5|6|7|U|8|@$9|V|A|W|B|C]]|D|@]|E|$]]|$1|F|3|G|5|6|7|X|8|@]|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|P|5|J|7|10|8|@]|D|@]|E|$K|L]]|$1|Q|3|R|5|6|7|11|8|@]|D|@]|E|$]]|$1|S|3|-4|5|6|7|12|8|@]|D|@]|E|$]]]|T|$]]

In my case, I was trying the same import in <code>manage.py shell</code>. The shell was messed up with the updated db. I mean, I forgot to restart my shell after updating the DB.
To resolve the issue, I had to stop the shell by the following command:
<pre class="lang-sh prettyprint-override"><code>&gt;&gt;&gt; exit()
</code></pre>
then restart the shell by the following command:
<pre><code>$ python3 manage.py shell

</code></pre>
Hope this will help somebody like me.

I'm at wit's end. After a dozen hours of troubleshooting, probably more, I thought I was finally in business, but then I got:

<pre><code>Model class django.contrib.contenttypes.models.ContentType doesn't declare an explicit app_label 
</code></pre>

There is SO LITTLE info on this on the web, and no solution out there has resolved my issue. Any advice would be tremendously appreciated.

I'm using Python 3.4 and Django 1.10.

From my settings.py:

<pre><code>INSTALLED_APPS = [
 'DeleteNote.apps.DeletenoteConfig',
 'LibrarySync.apps.LibrarysyncConfig',
 'django.contrib.admin',
 'django.contrib.auth',
 'django.contrib.contenttypes',
 'django.contrib.sessions',
 'django.contrib.messages',
 'django.contrib.staticfiles',
]
</code></pre>

And my apps.py files look like this:

<pre><code>from django.apps import AppConfig


class DeletenoteConfig(AppConfig):
 name = 'DeleteNote'
</code></pre>

and

<pre><code>from django.apps import AppConfig


class LibrarysyncConfig(AppConfig):
 name = 'LibrarySync'
</code></pre>

Django model "doesn't declare an explicit app_label"

数据库

服务器

Django

Python

我已经无计可施了。经过十几个小时的故障排除，也许更多，我以为我终于可以开始做生意了，但后来我得到了：Model class django.contrib.contenttypes.models.ContentType doesn't declare an explicit app_label 网上关于这方面的信息太少了...

问Django模型“没有声明显式的app_label”
EN

社区

活动

资源

关于

腾讯云开发者

热门产品

热门推荐

更多推荐

问Django模型“没有声明显式的app_label”EN

社区

活动

资源

关于

腾讯云开发者

热门产品

热门推荐

更多推荐

问Django模型“没有声明显式的app_label”
EN