0.8.3 (2011-02-10)
Change conditional usage of ZCML registrations for views to use ‘have’ instead of ‘installed’ to account for consumers of zope.app.form which aren’t using the meta.zcml of that package.
Display this changelog on PyPI.
0.8.2 (2011-01-25)
Actually remove zope.app.testing from the non-testing dependencies!
0.8.1 (2011-01-25)
Make registration of ZCML forms conditional on the presence of zope.app.form. This is probably a deprecated feature by now.
0.8 (2011-01-25)
Changes to use the ZTK import locations.
Use newer version of openldap for test builds.
zest.releaser support in buildout
Reduce dependencies. zope.app.testing dependency still exists, though, and should be removed by adjusting the tests.
0.7 - 04.07.2008
Updated install_requires to include all dependencies.
Removed deprecated localUtility ZCML.
buildout.cfg compiles openldap and creates a python-ldap egg
Compatible with Grok 0.12 and 0.13 releases.
0.6 - 20.11.2006
Fixed Zope 3.3 induced deprecation warnings.
principalInfo will try to look up a group if it cannot find a user. This is to make ldappas support groups in a minimal way. It is still the responsibility of the application to add LDAP-based groups to the principal (for instance by subscribing to the IAuthenticatedPrincipalCreated).
Release files for ldappas 0.8.3
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 |
|---|---|---|---|---|
| ldappas-0.8.3.tar.gz | 10.9 kB | Without provenance | Details for ldappas-0.8.3.tar.gz |
Release files / ldappas-0.8.3.tar.gz
| Download URL | ldappas-0.8.3.tar.gz |
|---|---|
| Size | 10.9 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
81bf0d6fa322b0d45630eeee36a237a4893af761ce95589f45b7e02e9a02a056
|
|
BLAKE2b-256 checksum How to use checksums |
9ac8e2533d99254a7acffd459fa7ac3ff223af9dcf00c276255dcfeaf04a0f9e
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
Security for ldappas 0.8.3
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.
