zope.principalregistry
This package provides an authentication utility for zope.authentication that uses a simple non-persistent principal registry. This is typically registered as a global utility, and it is usually configured in ZCML.
Documentation is hosted at https://zopeprincipalregistry.readthedocs.io
Changes
6.0 (2025-09-12)
Replace pkg_resources namespace with PEP 420 native namespace.
5.1 (2025-02-14)
Add support for Python 3.12, 3.13.
Drop support for Python 3.7, 3.8.
5.0 (2023-07-06)
Drop support for Python 2.7, 3.5, 3.6.
Drop support for deprecated python setup.py test.
Add support for Python 3.11.
4.3 (2022-07-14)
Drop support for Python 3.4.
Add support for Python 3.7, 3.8, 3.9, 3.10.
4.2.0 (2017-10-01)
Fix principal and group objects registered in ZCML or directly with the principalregistry being invalid under Python 2 (having byte strings for id instead of text strings). See https://github.com/zopefoundation/zope.principalregistry/issues/7
4.1.0 (2017-09-04)
Add support for Python 3.5 and 3.6.
Drop support for Python 2.6 and 3.3.
Host documentation at https://zopeprincipalregistry.readthedocs.io
Reach 100% test coverage and ensure we remain there.
Test PyPy3 on Travis CI.
4.0.0 (2014-12-24)
Add support for PyPy. (PyPy3 is pending release of a fix for: https://bitbucket.org/pypy/pypy/issue/1946)
Add support for Python 3.4.
Add support for testing under Travis.
4.0.0a2 (2013-03-03)
Make sure that the password is always bytes when passed into the principal registry.
Fix deprecation warnings.
4.0.0a1 (2013-02-22)
Add support for Python 3.3.
Replace deprecated zope.interface.implements usage with equivalent zope.interface.implementer decorator.
Dropd support for Python 2.4 and 2.5.
3.7.1 (2010-09-25)
Add test extra to declare test dependency on zope.component [test].
Use Python’s doctest module instead of deprecated zope.testing.doctest.
3.7.0 (2009-03-14)
Remove zope.container dependency, as contained principals didn’t make any sense, since PrincipalRegistry never provided IContainer. Also, zope.container pulls a number dependencies, that are not needed for non-persistent principal registry (like, ZCML, for example).
Set __name__ and __parent__ by hand to provide some backward-compatibility and to save a pointer to registry from principal objects.
Initial release. This package was split from zope.app.security as a part of the refactoring process to provide global principal registry without extra dependencies.
Metadata
Release files for zope.principalregistry 6.0
For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.
Source distribution (sdist)
| File | Size | Uploaded | Provenance | |
|---|---|---|---|---|
| zope_principalregistry-6.0.tar.gz | 22.7 kB | Without provenance | Details |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Reset |
|---|---|---|---|---|
| zope_principalregistry-6.0-py3-none-any.whl | Python 3 | none | any | Details |
Total release size: 38.5 kB
Release files / zope_principalregistry-6.0.tar.gz
| Download URL | zope_principalregistry-6.0.tar.gz |
|---|---|
| Size | 22.7 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
57d5f74af7506fa37dc29ab39ca16d80083e6f8d1c4c862ac715cc0602fe842b
|
|
BLAKE2b-256 checksum How to use checksums |
becba8b9a489c6621ab684059493f851314b3cb3f64fdd6fb55542d907e39be0
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/6.1.0 CPython/3.12.11
|
Release files / zope_principalregistry-6.0-py3-none-any.whl
| Download URL | zope_principalregistry-6.0-py3-none-any.whl |
|---|---|
| Size | 15.8 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
648e8965cf96ce602189ae281a2adfbc72d4f4ffca7b826e7af826b7fac91044
|
|
BLAKE2b-256 checksum How to use checksums |
2a94e6e2ec31267df486e91827dbe6a5405665b13d5f147ba647628b543909cd
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/6.1.0 CPython/3.12.11
|
Security for zope.principalregistry 6.0
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
No provenance found
None of the files in this release were uploaded with provenance metadata.
A note on package security
PyPI is a repository for distributing packages, not a service for auditing them. While third-party security researchers and our staff do their best to detect and remove malicious packages, PyPI cannot guarantee the quality, security or suitability of any given package.
To learn more about protecting yourself from malicious actors, visit our package security documentation.
