This release is a pre-release and may not be stable for production use.
Introduction
This package registers an event handler that initialises permissions on the fly. To use it, simply include its ZCML:
<include package="collective.autopermission" />
Then, you can use the <permission /> ZCML statement to define a new type of permission, without also needing to make the permission “spring into existence” via ClassSecurityInfo or similar.
Changelog
1.0b2 (2011-05-02)
Fix deprecation warning
Fix pep8
1.0b1 - March 11, 2009
Initial release
Metadata
Release files for collective.autopermission 1.0b2
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 | Actions |
|---|---|---|---|---|
| collective.autopermission-1.0b2.tar.gz | 2.9 kB | Without provenance | Details for collective.autopermission-1.0b2.tar.gz |
Release files / collective.autopermission-1.0b2.tar.gz
| Download URL | collective.autopermission-1.0b2.tar.gz |
|---|---|
| Size | 2.9 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
cd4dd40549927904ddf38acc14b1979ee3dc95e77a05b41d1aa691d4b03aefe6
|
|
BLAKE2b-256 checksum How to use checksums |
72cf4e79bad16f287807c0565f57696fa1e08f3f9371b3b3aae6ec2631440271
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
Security for collective.autopermission 1.0b2
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.