這是老 - 但以供將來參考 - 期望的行爲是工作的開箱現在(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