288b5df808
based on repoze.who (which deals with authentication and identification). On the one hand, it enables an authorization system based on the groups to which the `authenticated or anonymous` user belongs and the permissions granted to such groups by loading these groups and permissions into the request on the way in to the downstream WSGI application. And on the other hand, it enables you to manage your groups and permissions from the application itself or another program, under a backend-independent API. For example, it would be easy for you to switch from one back-end to another, and even use this framework to migrate the data. WWW: http://what.repoze.org/docs/1.x/ PR: ports/137459 Submitted by: Wen Heping <wenheping at gmail.com>
3 lines
207 B
Text
3 lines
207 B
Text
MD5 (repoze.what-1.0.8.tar.gz) = 2e9659f4d23711f41017cd4a26d76848
|
|
SHA256 (repoze.what-1.0.8.tar.gz) = b4fb50d444866dc1410a4b9d04f9a05762f756b58f4f67b767b470f77f74a6db
|
|
SIZE (repoze.what-1.0.8.tar.gz) = 58980
|