django-object-permissions vs django-guardian Vs django-authority [英] django-object-permissions Vs django-guardian Vs django-authority

问题描述

我发现了Django 1.2 + 3的行级许可解决方案

• django-object-permissions


• django-guardian


• django-authority

有人可以告诉是否有任何建议超过其他人，他们的主要区别是什么？？

解决方案

对象级许可 - 我们使用自己的自定义方法，我真的希望我们没有。如果你可以避免对象级别的权限，那么这样做是很困难的。

这是我评估你提到的3个应用程序的方式。 p>

积极发展：

1. django-guardian（1周前）


2. django-object-permissions（1年前）


3. django-authority（近2年前）

API

1. django-guardian（保存定义模型的实例）


2. django-object-permissions（注册权限）


3. django-authority（定义类）

上面是顺序的顺序。

我建议监护人纯粹在API上，但事实上它仍在开发中其他人通常不是一个大胜利。

I've found 3 row-level permission solutions for Django 1.2+

• django-object-permissions
• django-guardian
• django-authority

Could someone tell if there is any recommended more than the others, what are their main differences, etc.?

解决方案

I'll start this by saying we use none of these for object level permission - we use our own custom method and I really wish we hadn't. If you can avoid object level permissions at all, do so, they are a pain to organise.

This is how I evaluate the 3 apps you've mentioned.

Active Development:

1. django-guardian (1 week ago)
2. django-object-permissions (1 year ago)
3. django-authority (nearly 2 years ago)

API

1. django-guardian (save an instance of a defined model)
2. django-object-permissions (register permissions)
3. django-authority (define classes)

The above are in order by the way.

I'd recommend guardian purely on API alone, but the fact that it is still being developed where the others aren't usually means a big win.

这篇关于django-object-permissions vs django-guardian Vs django-authority的文章就介绍到这了，希望我们推荐的答案对大家有所帮助，也希望大家多多支持IT屋！