Zope.securitypolicy

Latest version: v5.0

Safety actively analyzes 681866 Python packages for vulnerabilities to keep your Python projects secure.

Scan your dependencies

Page 3 of 3

3.5.1

==================

- Don't depend on the ``hook`` extra of zope.component, as we don't need
it explicitly.

- Import security settings (Allow, Deny, Unset) in the ``interfaces``
module from the ``zope.securitypolicy.settings``, added in previous
release instead of old ``zope.app.security.settings``.
The ``zope.app.security`` will be adapted to import them from
``zope.securitypolicy.interfaces``.

- Use ``_z_instances`` instead of ``__instances__`` for storing instances
for ``zope.securitypolicy.settings.PermissionSetting`` singleton
implementation, because __*__ name pattern is reserved for special
names in python.

- Add security protections for the ``PermissionSetting``.

- Improve documentation formatting, add it to the package's long
description.

- Remove unneeded dependencies.

- Remove old zpkg-related files and zcml slugs.

3.5.0

==================

- Include settings that were previously imported from zope.app.security.

3.4.2

==================

- Change mailing list address to zope-dev at zope.org. Fix package
homepage to the pypi page.

- Fix test in buildout which still depended on zope.app.securitypolicy
by mistake.

- Remove explicit dependency on zope.app.form from ``setup.py``; nothing
in the code directly depends on this.

3.4.1

==================

- Fix reference to deprecated security policy from ZCML.

3.4.0

==================

- Initial documented release

Page 3 of 3

© 2024 Safety CLI Cybersecurity Inc. All Rights Reserved.