Parents (Total: 25)

The searched file hash is included in 25 parent files which include package known and seen by metalookup. A sample is included below:

Key	Value
MD5	9D410EA11E03B322925DE9DF4703B200
PackageArch	noarch
PackageDescription	`repoze.what` is an `authorization framework` for WSGI applications, based on `repoze.who` (which deals with `authentication`). 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. It's highly extensible, so it's very unlikely that it will get in your way. Among other things, you can extend it to check for many other conditions (such as checking that the user comes from a given country, based on her IP address, for example).
PackageMaintainer	Fedora Project
PackageName	python-repoze-what
PackageRelease	5.fc19
PackageVersion	1.0.9
SHA-1	070F45F06BE797853C004A86D3C07B6F8E8BA715
SHA-256	00BB5CBFBCC601305150347D00BCB975D354B4FF787BCA16AACFF9F0831F7A29

Key	Value
MD5	C6920F53DCCB6DD5C13794F50D9CC740
PackageArch	noarch
PackageDescription	`repoze.what` is an `authorization framework` for WSGI applications, based on `repoze.who` (which deals with `authentication`). 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. It's highly extensible, so it's very unlikely that it will get in your way. Among other things, you can extend it to check for many other conditions (such as checking that the user comes from a given country, based on her IP address, for example).
PackageMaintainer	Fedora Project
PackageName	python-repoze-what
PackageRelease	4.fc18
PackageVersion	1.0.9
SHA-1	0EF917C066280FDA47C9DC0E89B67CD9D2BDC940
SHA-256	13F848152EE0857EED959755F25160D15931DD8066E358E439DB726A5A68FBB0

Key	Value
MD5	7E456AA6C6021D28F304F0092ABD8BAC
PackageArch	noarch
PackageDescription	`repoze.what` is an `authorization framework` for WSGI applications, based on `repoze.who` (which deals with `authentication`). 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. It's highly extensible, so it's very unlikely that it will get in your way. Among other things, you can extend it to check for many other conditions (such as checking that the user comes from a given country, based on her IP address, for example).
PackageMaintainer	Fedora Project
PackageName	python-repoze-what
PackageRelease	5.fc19
PackageVersion	1.0.9
SHA-1	14CF0FA408D86AA7FEDAD6175DBCD509062B574A
SHA-256	2995AA27805467DFF8E7540247F7C052B10EFE1D47BE8BCEE53B1000F85CC7B9

Key	Value
MD5	744B0C9A6647C41BC15A3DFFCEE222C0
PackageArch	noarch
PackageDescription	`repoze.what` is an `authorization framework` for WSGI applications, based on `repoze.who` (which deals with `authentication`). 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. It's highly extensible, so it's very unlikely that it will get in your way. Among other things, you can extend it to check for many other conditions (such as checking that the user comes from a given country, based on her IP address, for example).
PackageMaintainer	Fedora Project
PackageName	python-repoze-what
PackageRelease	5.fc19
PackageVersion	1.0.9
SHA-1	1EC710E091A5752E9A6B64BA07B017260CC9B0EE
SHA-256	FE3402DC9B376F8B7F54598FC253ABC7D9474F08B772DA1BF7FFA31732E4F530

Key	Value
MD5	935C54BEA287CF6C48005D6C8BAE130C
PackageArch	noarch
PackageDescription	`repoze.what` is an `authorization framework` for WSGI applications, based on `repoze.who` (which deals with `authentication`). 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. It's highly extensible, so it's very unlikely that it will get in your way. Among other things, you can extend it to check for many other conditions (such as checking that the user comes from a given country, based on her IP address, for example).
PackageMaintainer	Fedora Project
PackageName	python-repoze-what
PackageRelease	5.fc19
PackageVersion	1.0.9
SHA-1	212824B5D39AA6A16ADFDE012FAAFDF4D5D4D89B
SHA-256	CE18ABC5CA7692A47B807E3AF7F320438865757277EF2E5F27B3377865E8F666

Key	Value
MD5	DCB83949C6E38CB9292B62333F4C52AA
PackageArch	noarch
PackageDescription	`repoze.what` is an `authorization framework` for WSGI applications, based on `repoze.who` (which deals with `authentication`). 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. It's highly extensible, so it's very unlikely that it will get in your way. Among other things, you can extend it to check for many other conditions (such as checking that the user comes from a given country, based on her IP address, for example).
PackageMaintainer	Fedora Project
PackageName	python-repoze-what
PackageRelease	2.fc15
PackageVersion	1.0.9
SHA-1	35971854869BE06B87067FF06EB66172DFECB3B7
SHA-256	B257C52610C914BA31261626910F930486FA18CE45B20441B1759B19842DA3D0

Key	Value
MD5	662A0BA156D9548C2F1D52C9C402CA52
PackageArch	noarch
PackageDescription	`repoze.what` is an `authorization framework` for WSGI applications, based on `repoze.who` (which deals with `authentication`). 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. It's highly extensible, so it's very unlikely that it will get in your way. Among other things, you can extend it to check for many other conditions (such as checking that the user comes from a given country, based on her IP address, for example).
PackageMaintainer	Fedora Project
PackageName	python-repoze-what
PackageRelease	3.fc17
PackageVersion	1.0.9
SHA-1	37D43BCD08B5A8B537B311397585E962B6D0A93D
SHA-256	68055A964346418AB40D99E3A99DC42207257ECAEF906DDAE8E48FAD1DC6EEFC

Key	Value
MD5	A95924ABDA6DF7FF70E3740C5B9CAB40
PackageArch	noarch
PackageDescription	`repoze.what` is an `authorization framework` for WSGI applications, based on `repoze.who` (which deals with `authentication`). 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. It's highly extensible, so it's very unlikely that it will get in your way. Among other things, you can extend it to check for many other conditions (such as checking that the user comes from a given country, based on her IP address, for example).
PackageMaintainer	Fedora Project
PackageName	python-repoze-what
PackageRelease	4.fc18
PackageVersion	1.0.9
SHA-1	3A5988133030C9BDD314224DB64358477B3AAC87
SHA-256	568D471660821BC1F17F626F5A5B4DAD3481E6EE8D105580D532EEBC7491D4CB

Key	Value
MD5	A2645DA3F5DEEABA0A67C70C4CA0A9D8
PackageArch	noarch
PackageDescription	`repoze.what` is an `authorization framework` for WSGI applications, based on `repoze.who` (which deals with `authentication`). 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. It's highly extensible, so it's very unlikely that it will get in your way. Among other things, you can extend it to check for many other conditions (such as checking that the user comes from a given country, based on her IP address, for example).
PackageMaintainer	Fedora Project
PackageName	python-repoze-what
PackageRelease	1.fc14
PackageVersion	1.0.9
SHA-1	56B660D6EC973C9B1D6E305E7C9D35C2D63BEEAF
SHA-256	5C5BDBDA9B861DDAB112D709B5E67BB629FF9E6EBABA795B1AD42C917FEBC4F9

Key	Value
FileSize	72732
MD5	52B46B7735CAF3D9AE106386E898AFD4
PackageDescription	authorization framework for Python WSGI applications repoze.what is an authorization framework for WSGI applications, 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 the programmer to manage groups and permissions from the application itself or another program, under a backend-independent API. For example, it would be easy to switch from one back-end to another, and even use this framework to migrate the data. . This is just the authorization pattern it supports out-of-the-box, but it supports other authorization patterns with custom predicates. It's highly extensible, so it's very unlikely that it will get in the way and can be extended to check for many conditions (e.g.: checking that the user comes from a given country, based on her IP address).
PackageMaintainer	Debian Python Modules Team <python-modules-team@lists.alioth.debian.org>
PackageName	python-repoze.what
PackageSection	python
PackageVersion	1.0.9-5
SHA-1	6511A3D26205005D3017E0334A75553E0CB36522
SHA-256	A026947670C373F350D786B62F1BA1056CF7EA98867D11640B00B527BF8B24F8