blocks|key|4503760|text|在深入研究这个问题之后，唯一对我有用的是|type|unstyled|depth|inlineStyleRanges|entityRanges|data|4503761|comment+out+the+offending+apps,+run+migrations,+then+add+them+in+again.|offset|length|style|CODE|4503762|这只是一种变通方法，但希望它能帮助某些人。|4503763|entityMap^0|0|0|1Z|0|0^^$0|@$1|2|3|4|5|6|7|L|8|@]|9|@]|A|$]]|$1|B|3|C|5|6|7|M|8|@$D|N|E|O|F|G]]|9|@]|A|$]]|$1|H|3|I|5|6|7|P|8|@]|9|@]|A|$]]|$1|J|3|-4|5|6|7|Q|8|@]|9|@]|A|$]]]|K|$]]

After a lot of digging on this the only thing that worked for me was

<code>comment out the offending apps, run migrations, then add them in again.</code>

Just a workaround but hopefully it helps somebody.

blocks|key|4504005|text|只需在应用程序的根目录(在您的示例中为users/migrations/+)创建一个migrations目录并添加一个空的__init__.py文件，就可以解决您的问题。当我遇到同样的错误时，至少对我来说是这样的。|type|unstyled|depth|inlineStyleRanges|offset|length|style|CODE|entityRanges|data|4504006|但你最好在你的应用程序上运行makemigrations，正如上面的@zenofewords所建议的那样。这将为您创建目录并为您的代理模型生成迁移。|4504007|Why+does+Django+create+migration+files+for+proxy+models?|4504008|您的测试正在寻找这些迁移，但没有找到它们。|4504009|entityMap|0|LINK|mutability|MUTABLE|url|https://stackoverflow.com/questions/37988914/why-does-django-create-migration-files-for-proxy-models^0|J|H|16|A|1P|B|0|E|E|0|0|1K|0|0|0^^$0|@$1|2|3|4|5|6|7|T|8|@$9|U|A|V|B|C]|$9|W|A|X|B|C]|$9|Y|A|Z|B|C]]|D|@]|E|$]]|$1|F|3|G|5|6|7|10|8|@$9|11|A|12|B|C]]|D|@]|E|$]]|$1|H|3|I|5|6|7|13|8|@]|D|@$9|14|A|15|1|16]]|E|$]]|$1|J|3|K|5|6|7|17|8|@]|D|@]|E|$]]|$1|L|3|-4|5|6|7|18|8|@]|D|@]|E|$]]]|M|$N|$5|O|P|Q|E|$R|S]]]]

Simply creating a <code>migrations</code> directory at the root of your app (so <code>users/migrations/</code> in your case) and adding an empty <code>__init__.py</code> file might resolve your issue. At least it did for me when I was getting the same error.

But you're better off running <code>makemigrations</code> for your app, as suggested by 
@zenofewords above. That will create the directory for you AND generate migrations for your proxy models.

<a href="https://stackoverflow.com/questions/37988914/why-does-django-create-migration-files-for-proxy-models">Why does Django create migration files for proxy models?</a>

Your tests are looking for those migrations and aren't finding them.

blocks|key|4503929|text|我遇到过这个问题，由于注释掉模型并不是一个真正的解决方案，我发现将未记录的auto_created+=+True设置为Meta类会使Django忽略它。|type|unstyled|depth|inlineStyleRanges|offset|length|style|CODE|entityRanges|data|4503930|class+GroupProxy(Group):

++++class+Meta:
++++++++proxy+=+True
++++++++auto_created+=+True|code-block|syntax|javascript|4503931|entityMap^0|11|J|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've come across this issue, and as commenting out the model isn't really a solution, I've found that setting the undocumented <code>auto_created = True</code> to the Meta class will make Django ignore it.

<pre><code>class GroupProxy(Group):

 class Meta:
 proxy = True
 auto_created = True
</code></pre>

blocks|key|4503673|text|在运行测试之前，您是否尝试过在应用程序上运行manage.py+makemigrations+<app_label>？|type|unstyled|depth|inlineStyleRanges|offset|length|style|CODE|entityRanges|data|4503674|此外，检查您尝试代理的应用程序是否包含在您的INSTALLED_APPS中。|4503675|entityMap^0|M|10|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|$]]

Have you tried running <code>manage.py makemigrations &lt;app_label&gt;</code> on your app before running tests?

Also, check if the app which model(s) you are trying to Proxy is included in your INSTALLED_APPS.

blocks|key|4504546|text|添加一个名为"migrations“的文件夹，并在该文件夹中创建"__init__.py”文件|type|unstyled|depth|inlineStyleRanges|offset|length|style|CODE|entityRanges|data|4504547|entityMap^0|7|A|X|B|0^^$0|@$1|2|3|4|5|6|7|H|8|@$9|I|A|J|B|C]|$9|K|A|L|B|C]]|D|@]|E|$]]|$1|F|3|-4|5|6|7|M|8|@]|D|@]|E|$]]]|G|$]]

add a folder named &quot;<code>migrations</code>&quot; and in this folder create &quot;<code>__init__.py</code>&quot; file

blocks|key|4504107|text|我也面临着这个问题(在做了一些复杂的模型继承之后)。我的一个迁移包含|type|unstyled|depth|inlineStyleRanges|entityRanges|data|4504108|migrations.CreateModel(
++++name='Offer',
++++fields=[
++++++++#+...
++++],
++++options={
++++++++#+...
++++},
++++bases=('shop.entity',),
),|code-block|syntax|javascript|4504109|我完全删除了shop.Entity模型，但迁移在bases属性中引用了它。所以我删除了bases=('shop.entity',)，它起作用了。它可能会打破从一开始迁移的机会，但至少允许进一步迁移。|offset|length|style|CODE|4504110|另一个建议是:直接转到django代码，检查是什么导致了“base”问题。转到django/db/migrations/state.py并添加断点：|4504111|try:
++++bases+=+tuple(
++++++++(apps.get_model(base)+if+isinstance(base,+six.string_types)+else+base)
++++++++for+base+in+self.bases
++++)
except+LookupError:
++++print(self.bases)++#+<--+print+the+bases
++++import+ipdb;+ipdb.set_trace()++#+<--+debug+here
++++raise+InvalidBasesError("Cannot+resolve+one+or+more+bases+from+%25r"+%25+(self.bases,))|4504112|entityMap^0|0|0|6|B|O|5|17|M|0|13|T|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|@$I|V|J|W|K|L]|$I|X|J|Y|K|L]|$I|Z|J|10|K|L]]|9|@]|A|$]]|$1|M|3|N|5|6|7|11|8|@$I|12|J|13|K|L]]|9|@]|A|$]]|$1|O|3|P|5|D|7|14|8|@]|9|@]|A|$E|F]]|$1|Q|3|-4|5|6|7|15|8|@]|9|@]|A|$]]]|R|$]]

I also faced this issue (after doing some complex model inheritance). One of my migrations contained 

<pre><code>migrations.CreateModel(
 name='Offer',
 fields=[
 # ...
 ],
 options={
 # ...
 },
 bases=('shop.entity',),
),
</code></pre>

I deleted <code>shop.Entity</code> model entirely, but the migration was referencing it in <code>bases</code> attribute. So I just deleted <code>bases=('shop.entity',)</code> and it works. It will probably break an opportunity to migrate from the beginning, but at least allows to migrate further on.

Another advice would be: go directly to django code and inspect what's causing "bases" trouble. Go to <code>django/db/migrations/state.py</code> and add a breakpoint:

<pre><code>try:
 bases = tuple(
 (apps.get_model(base) if isinstance(base, six.string_types) else base)
 for base in self.bases
 )
except LookupError:
 print(self.bases) # &lt;-- print the bases
 import ipdb; ipdb.set_trace() # &lt;-- debug here
 raise InvalidBasesError("Cannot resolve one or more bases from %r" % (self.bases,))
</code></pre>

blocks|key|4503814|text|如果只在运行python+manage.py+test时发生这种情况(可能是因为您已经进行了必要的迁移)，那么您应该在设置模块的MIGRATION_MODULES中明确说明不应该迁移contrib.auth。|type|unstyled|depth|inlineStyleRanges|offset|length|style|CODE|entityRanges|data|4503815|MIGRATION_MODULES(
++++++++'auth':+"contrib.auth.migrations_not_used_in_tests",
)|code-block|syntax|javascript|4503816|entityMap^0|6|L|1S|H|2J|C|0|0^^$0|@$1|2|3|4|5|6|7|M|8|@$9|N|A|O|B|C]|$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|-4|5|6|7|U|8|@]|D|@]|E|$]]]|L|$]]

If this is only happening when running <code>python manage.py test</code> (maybe because you have already made the necessary migrations), you should explicitly say that <code>contrib.auth</code> should not migrate in the <code>MIGRATION_MODULES</code> of your settings module.

<pre><code>MIGRATION_MODULES(
 'auth': "contrib.auth.migrations_not_used_in_tests",
)
</code></pre>

blocks|key|4504157|text|一种可能是在迁移文件中删除或创建模型的顺序错误。当基本模型在派生模型之前时，我在Django+1.7.8中经历了这一点。交换删除模型的顺序已修复此问题。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|4504158|entityMap^0|0^^$0|@$1|2|3|4|5|6|7|D|8|@]|9|@]|A|$]]|$1|B|3|-4|5|6|7|E|8|@]|9|@]|A|$]]]|C|$]]

One possibility is that the deleting or creating of a model in the migration file is in the wrong order. I experienced this in Django 1.7.8 when the base model was BEFORE the derived model. Swapping the order for deleting the model fixed the issue.

blocks|key|4504350|text|在没有其他应用程序的情况下发生在我身上-只是因为我重命名了一个模型，该模型是其他模型的基础(并且可能在同一迁移中创建子模型)将超级模型重命名为它的原始名称为我解决了它|type|unstyled|depth|inlineStyleRanges|entityRanges|data|4504351|entityMap^0|0^^$0|@$1|2|3|4|5|6|7|D|8|@]|9|@]|A|$]]|$1|B|3|-4|5|6|7|E|8|@]|9|@]|A|$]]]|C|$]]

happened to me with no other app - just because I renamed a model which was a base for other models (and maybe created that sub-models within the same migration) renaming the super-model to it's original name solved it for me

blocks|key|4504414|text|我遇到了同样的问题，在class+Meta:中添加app_label属性解决了这个错误：|type|unstyled|depth|inlineStyleRanges|offset|length|style|CODE|entityRanges|data|4504415|class+GroupProxy(Group):
++++class+Meta:
++++++++proxy+=+True
++++++++app_label+=+'<app+in+which+you+want+this+model>'
++++++++verbose_name+=+Group._meta.verbose_name
++++++++verbose_name_plural+=+Group._meta.verbose_name_plural|code-block|syntax|javascript|4504416|entityMap^0|B|B|P|9|0|0^^$0|@$1|2|3|4|5|6|7|M|8|@$9|N|A|O|B|C]|$9|P|A|Q|B|C]]|D|@]|E|$]]|$1|F|3|G|5|H|7|R|8|@]|D|@]|E|$I|J]]|$1|K|3|-4|5|6|7|S|8|@]|D|@]|E|$]]]|L|$]]

I faced the same issue and adding <code>app_label</code> attribute in <code>class Meta:</code> solved the error :

<pre><code>class GroupProxy(Group):
 class Meta:
 proxy = True
 app_label = '&lt;app in which you want this model&gt;'
 verbose_name = Group._meta.verbose_name
 verbose_name_plural = Group._meta.verbose_name_plural
</code></pre>

blocks|key|4504491|text|为了防止有人犯了和我一样的错误，我也遇到了同样的问题，因为我没有对代理模型进行任何迁移。对我来说，这似乎没有必要，因为他们没有自己的DB表，而且我在文档中也没有看到任何提到这一点的内容。python+manage.py+makemigrations+<APP_NAME>把它修好了。|type|unstyled|depth|inlineStyleRanges|offset|length|style|CODE|entityRanges|data|4504492|entityMap^0|2L|16|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|$]]

Just incase anyone made the same mistake as me, I had the same issue because I hadn't made any migrations for the Proxy models. It didn't seem necessary to me as they don't have their own DB tables and I didn't see anything mentioning this in the docs. <code>python manage.py makemigrations &lt;APP_NAME&gt;</code> fixed it right up.

blocks|key|4504579|text|还有一个相关的问题。请在此处查看我的答案https://stackoverflow.com/a/67500550/502045|type|unstyled|depth|inlineStyleRanges|entityRanges|offset|length|data|4504580|TL;DR|4504581|创建您自己的操作来删除基数|4504582|class+RemoveModelBasesOptions(ModelOptionOperation):
++++def+__init__(self,+name):
++++++++super().__init__(name)

++++def+deconstruct(self):
++++++++kwargs+=+{
++++++++++++'name':+self.name,
++++++++}
++++++++return+(
++++++++++++self.__class__.__qualname__,
++++++++++++[],
++++++++++++kwargs
++++++++)

++++def+state_forwards(self,+app_label,+state):
++++++++model_state+=+state.models[app_label,+self.name_lower]
++++++++model_state.bases+=+(models.Model,)
++++++++state.reload_model(app_label,+self.name_lower,+delay=True)

++++def+database_forwards(self,+app_label,+schema_editor,+from_state,
++++++++++++++++++++++++++to_state):
++++++++pass

++++def+database_backwards(self,+app_label,+schema_editor,+from_state,
+++++++++++++++++++++++++++to_state):
++++++++pass

++++def+describe(self):
++++++++return+"Remove+bases+from+the+model+%25s"+%25+self.name

++++@property
++++def+migration_name_fragment(self):
++++++++return+'remove_%25s_bases'+%25+self.name_lower|code-block|syntax|javascript|4504583|entityMap|0|LINK|mutability|MUTABLE|url|https://stackoverflow.com/a/67500550/502045^0|K|17|0|0|0|0|0^^$0|@$1|2|3|4|5|6|7|U|8|@]|9|@$A|V|B|W|1|X]]|C|$]]|$1|D|3|E|5|6|7|Y|8|@]|9|@]|C|$]]|$1|F|3|G|5|6|7|Z|8|@]|9|@]|C|$]]|$1|H|3|I|5|J|7|10|8|@]|9|@]|C|$K|L]]|$1|M|3|-4|5|6|7|11|8|@]|9|@]|C|$]]]|N|$O|$5|P|Q|R|C|$S|T]]]]

There's a related question. See my answer here <a href="https://stackoverflow.com/a/67500550/502045">https://stackoverflow.com/a/67500550/502045</a>
TL;DR
Create your own operation to remove bases
<pre class="lang-py prettyprint-override"><code>class RemoveModelBasesOptions(ModelOptionOperation):
 def __init__(self, name):
 super().__init__(name)

 def deconstruct(self):
 kwargs = {
 'name': self.name,
 }
 return (
 self.__class__.__qualname__,
 [],
 kwargs
 )

 def state_forwards(self, app_label, state):
 model_state = state.models[app_label, self.name_lower]
 model_state.bases = (models.Model,)
 state.reload_model(app_label, self.name_lower, delay=True)

 def database_forwards(self, app_label, schema_editor, from_state,
 to_state):
 pass

 def database_backwards(self, app_label, schema_editor, from_state,
 to_state):
 pass

 def describe(self):
 return &quot;Remove bases from the model %s&quot; % self.name

 @property
 def migration_name_fragment(self):
 return 'remove_%s_bases' % self.name_lower
</code></pre>

blocks|key|4504615|text|您可能必须在没有迁移的情况下为应用程序运行makemigrations。|type|unstyled|depth|inlineStyleRanges|offset|length|style|CODE|entityRanges|data|4504616|在我的例子中，django_quiz依赖于multichoice、true_false和essay。|4504617|在我可以migrate+django_quiz之前，我必须对每一个都执行makemigrations。|4504618|entityMap^0|L|E|0|7|B|L|B|X|A|18|5|0|4|7|10|E|0^^$0|@$1|2|3|4|5|6|7|L|8|@$9|M|A|N|B|C]]|D|@]|E|$]]|$1|F|3|G|5|6|7|O|8|@$9|P|A|Q|B|C]|$9|R|A|S|B|C]|$9|T|A|U|B|C]|$9|V|A|W|B|C]]|D|@]|E|$]]|$1|H|3|I|5|6|7|X|8|@$9|Y|A|Z|B|C]|$9|10|A|11|B|C]]|D|@]|E|$]]|$1|J|3|-4|5|6|7|12|8|@]|D|@]|E|$]]]|K|$]]

You may have to run <code>makemigrations</code> for the apps without migrations.
In my case <code>django_quiz</code> depends on <code>multichoice</code>, <code>true_false</code> and <code>essay</code>.
I had to <code>makemigrations</code> for each of these before I could <code>migrate</code> django_quiz.

When I run tests I get this error during database initialization:

<pre><code>django.db.migrations.state.InvalidBasesError: Cannot resolve bases for [&lt;ModelState: 'users.GroupProxy'&gt;]
This can happen if you are inheriting models from an app with migrations (e.g. contrib.auth)
</code></pre>

I created this proxy for contrib.auth Group model to place it in my app in django admin:

<pre><code>class GroupProxy(Group):
 class Meta:
 proxy = True
 verbose_name = Group._meta.verbose_name
 verbose_name_plural = Group._meta.verbose_name_plural
</code></pre>

So what can I do to fix this issue?

InvalidBasesError: Cannot resolve bases for [<ModelState: 'users.GroupProxy'>]

当我运行测试时，我在数据库初始化期间得到以下错误：django.db.migrations.state.InvalidBasesError: Cannot resolve bases for [<ModelState: 'users.GroupProxy'>]This can happen if you are inheriting models from an app with migratio

问InvalidBasesError:无法解析[<模型状态：'users.GroupProxy'>]的基
EN

回答 13

Stack Overflow用户

Stack Overflow用户

Stack Overflow用户

社区

活动

资源

关于

腾讯云开发者

热门产品

热门推荐

更多推荐

问InvalidBasesError:无法解析[<模型状态：'users.GroupProxy'>]的基EN

回答 13

Stack Overflow用户

Stack Overflow用户

Stack Overflow用户

社区

活动

资源

关于

腾讯云开发者

热门产品

热门推荐

更多推荐

问InvalidBasesError:无法解析[<模型状态：'users.GroupProxy'>]的基
EN