Parents (Total: 184)

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

Key	Value
MD5	FA37241BCA63215E38E95F8C90E2E8E3
PackageArch	noarch
PackageDescription	repoze.who is an identification and authentication framework for arbitrary WSGI applications. It acts as WSGI middleware. repoze.who is inspired by Zope 2's Pluggable Authentication Service (PAS) (but repoze.who is not dependent on Zope in any way; it is useful for any WSGI application). It provides no facility for authorization (ensuring whether a user can or cannot perform the operation implied by the request). This is considered to be the domain of the WSGI application.
PackageMaintainer	Fedora Project
PackageName	python3-repoze-who
PackageRelease	4.fc21
PackageVersion	2.1
SHA-1	00CE9369C10082968FE326AA352DE7EB17147FC7
SHA-256	8D1228A383DF16336B14CF614110F32F96756388980EC02046EA5500F333FDB9

Key	Value
MD5	27C43704C30F7782B6566AADA716BA34
PackageArch	noarch
PackageDescription	repoze.who is an identification and authentication framework for arbitrary WSGI applications. It acts as WSGI middleware. repoze.who is inspired by Zope 2's Pluggable Authentication Service (PAS) (but repoze.who is not dependent on Zope in any way; it is useful for any WSGI application). It provides no facility for authorization (ensuring whether a user can or cannot perform the operation implied by the request). This is considered to be the domain of the WSGI application.
PackageMaintainer	Fedora Project
PackageName	python-repoze-who
PackageRelease	7.fc24
PackageVersion	2.1
SHA-1	01D679D84F1C7EEB8F8DC4F0B72EB983D38FBFCD
SHA-256	48FBF6121DA4A5E81534013733644FC3D480D959D93D20CD1F5F6A08D25B11B2

Key	Value
MD5	0D3A9669E4ED2F9B2F85EC14BB9882FA
PackageArch	noarch
PackageDescription	The ZODB transaction manager is a completely generic transaction manager. It can be used independently of the actual "object database" part of ZODB. One of the purposes of creating repoze.tm was to allow for systems other than Zope to make use of two-phase commit transactions in a WSGI context.
PackageMaintainer	Fedora Project
PackageName	python-repoze-tm2
PackageRelease	0.10.b1.fc17
PackageVersion	1.0
SHA-1	04B3B6314B8023E4D2D32A426F27C03FE9446E46
SHA-256	75284043F33400F389849DFD28580308CD2816C13877A267A9A1D81E608775BB

Key	Value
MD5	25D5F728CBCA2BE3D3F21FC611265767
PackageArch	noarch
PackageDescription	The ZODB transaction manager is a completely generic transaction manager. It can be used independently of the actual "object database" part of ZODB. One of the purposes of creating repoze.tm was to allow for systems other than Zope to make use of two-phase commit transactions in a WSGI context.
PackageMaintainer	Fedora Project
PackageName	python-repoze-tm2
PackageRelease	3.fc24
PackageVersion	2.0
SHA-1	0734AAB31CC0E7F15486FCD7E22CBFE15C15A031
SHA-256	73047CF85ACE122AFABADD296F2C7803229E163755F7DA23ECFD5B60826B844D

Key	Value
MD5	A5E28E53BF15BAECF3BE8EF91BA52B9B
PackageArch	noarch
PackageDescription	repoze.who is an identification and authentication framework for arbitrary WSGI applications. repoze.who can be configured either as WSGI middleware or as an API for use by an application. repoze.who is inspired by Zope 2's Pluggable Authentication Service (PAS) (but repoze.who is not dependent on Zope in any way; it is useful for any WSGI application). It provides no facility for authorization (ensuring whether a user can or cannot perform the operation implied by the request). This is considered to be the domain of the WSGI application.
PackageName	python3-repoze.who
PackageRelease	lp152.2.4
PackageVersion	2.4
SHA-1	08B2738E7DF1D1D82B7BADE64FB76B1966B9014A
SHA-256	A67634732C5380FFBED69E674202F3871A3BE371F6705810C7B2C54D3E1CB512

Key	Value
MD5	653AA01767AF4291D0C64212706A98B6
PackageArch	noarch
PackageDescription	repoze.who is an identification and authentication framework for arbitrary WSGI applications. repoze.who can be configured either as WSGI middleware or as an API for use by an application. repoze.who is inspired by Zope 2's Pluggable Authentication Service (PAS) (but repoze.who is not dependent on Zope in any way; it is useful for any WSGI application). It provides no facility for authorization (ensuring whether a user can or cannot perform the operation implied by the request). This is considered to be the domain of the WSGI application.
PackageName	python38-repoze.who
PackageRelease	17.24
PackageVersion	2.4
SHA-1	08EAAC8278FD43494B2B20D1960C4A19222D23AB
SHA-256	4CE768E328EE2730CC13A7272FEEF1689C6326F45088C8AB162E7B5FBB097829

Key	Value
MD5	AACCC2F936F3A09D9C7B2CC941F552A9
PackageArch	noarch
PackageDescription	The ZODB transaction manager is a completely generic transaction manager. It can be used independently of the actual "object database" part of ZODB. One of the purposes of creating repoze.tm was to allow for systems other than Zope to make use of two-phase commit transactions in a WSGI context.
PackageMaintainer	Fedora Project
PackageName	python-repoze-tm2
PackageRelease	0.5.a4.fc12
PackageVersion	1.0
SHA-1	0957C3E6D2C84943EC28E72F6309D79047A8278B
SHA-256	86753DF179E5AC5774DA40FF1149F0BD318D3F12A915B69FE42F8FB13E408796

Key	Value
MD5	15C462E3D765125A2FC4920452C44F99
PackageArch	noarch
PackageDescription	The ZODB transaction manager is a completely generic transaction manager. It can be used independently of the actual "object database" part of ZODB. One of the purposes of creating repoze.tm was to allow for systems other than Zope to make use of two-phase commit transactions in a WSGI context. This package contains the python3 version of the library.
PackageMaintainer	Fedora Project
PackageName	python3-repoze-tm2
PackageRelease	3.fc24
PackageVersion	2.0
SHA-1	0958AD126C20BFFCA41C43236DDC762CB71402E1
SHA-256	B9738520ACD903E64C8835194E764427FAB2E96F4E96E4E16D4F3409A2D40A19

Key	Value
MD5	3C8D101071CD90B3C1759269617D5568
PackageArch	noarch
PackageDescription	repoze.who is an identification and authentication framework for arbitrary WSGI applications. repoze.who can be configured either as WSGI middleware or as an API for use by an application. repoze.who is inspired by Zope 2's Pluggable Authentication Service (PAS) (but repoze.who is not dependent on Zope in any way; it is useful for any WSGI application). It provides no facility for authorization (ensuring whether a user can or cannot perform the operation implied by the request). This is considered to be the domain of the WSGI application.
PackageName	python38-repoze.who
PackageRelease	17.18
PackageVersion	2.4
SHA-1	0B02209508B5EEC05D115ACC77B66D974476F2A1
SHA-256	761525FFC8B9A0FE24531B58B516F32ED1D6782C0893DDA1C1DE29FF22C530ED

Key	Value
MD5	C63B6087ED6B891CDE0298699D135CA8
PackageArch	noarch
PackageDescription	repoze.who is an identification and authentication framework for arbitrary WSGI applications. repoze.who can be configured either as WSGI middleware or as an API for use by an application. repoze.who is inspired by Zope 2's Pluggable Authentication Service (PAS) (but repoze.who is not dependent on Zope in any way; it is useful for any WSGI application). It provides no facility for authorization (ensuring whether a user can or cannot perform the operation implied by the request). This is considered to be the domain of the WSGI application.
PackageName	python3-repoze.who
PackageRelease	lp153.2.1
PackageVersion	2.4
SHA-1	0BB8443A6F5CE27B187C10CB57B359B8945B8E5D
SHA-256	FD7B8D1B9E43E14E1A6F01752B7D56D9AEE37D481C1F3A2595B78B6976DA445B