这是老 - 但以供将来参考 - 期望的行为是工作的开箱现在(Django的1.9)
考虑具有相应权限的这种抽象模型:
class DetailContentLifecycleClassModel (models.Model):
class Meta:
abstract=True
permissions = (
('can_change_content', 'Change content of the model'),
('can_submit_for_approval', 'Ask for final check and publishing'),
('can_publish_content', 'Publish the model as a new version'),
)
当继承如下:
class Test_Details (DetailContentLifecycleClassModel):
name = models.CharField(max_length=200)
class Test_Details2 (DetailContentLifecycleClassModel):
name = models.CharField(max_length=200)
Permssions创建如下G:
from playground.models import Test_Details
from django.contrib.auth.models import User, Permission
tmp = Permission.objects.filter()
结果(这正是被通缉):
playground | test_ details | Can add test_ details
playground | test_ details | Change content of the model
playground | test_ details | Publish the model as a new version
playground | test_ details | Ask for final check and publishing
playground | test_ details | Can change test_ details
playground | test_ details | Can delete test_ details
playground | test_ details2 | Can add test_ details2
playground | test_ details2 | Change content of the model
playground | test_ details2 | Publish the model as a new version
playground | test_ details2 | Ask for final check and publishing
playground | test_ details2 | Can change test_ details2
playground | test_ details2 | Can delete test_ details2
这仍然是一个问题,但对于更近期来临的消息来说,这个问题隐约有利的是,这个问题在6个月前得到了一些工作,但还没有成为一个发布版本(我们在1.10 .5在写作时)。 https://github.com/django/django/pull/6861#issuecomment-240427426 – 2017-02-14 13:01:13