Grokcore.security

Latest version: v4.0

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

Scan your dependencies

Page 2 of 3

1.6.2

------------------

- Properly declare zope.dottedname as a dependency.

1.6.1

------------------

- Fix the package to properly work if the extra ``role`` is not
specified.

1.6

----------------

- The Permission and Role components moved from the grok package to the
grokcore.security package where it belongs.

- The permissions() directive moved from the grok package to
grokcore.security where it belongs.

1.5

----------------

- Upped the requirements for martian and grokcore.component.

- Made package comply to zope.org repository policy.

1.4

----------------

* **note** Backed out the version requirements for
grokcore.component-2.0 and martian-0.12. These requirements
stood in the way of further development especially towards
grok-1.1 based on the ZTK. The 1.3 version should probably
have been called 2.0 like with grokcore.component.

* Ported setup.py dependency fixes from trunk.

* Use zope.security instead of zope.app.security.

1.3

----------------

* Use the grok.zope.org/releaseinfo information instead of our own
copy of ``versions.cfg``, for easier maintenance.

* Depend on grokcore.component 2.0 and the 0.12 Martian - this changes
inheritance issues but doesn't appear to affect grokcore.security
itself.

Page 2 of 3

© 2024 Safety CLI Cybersecurity Inc. All Rights Reserved.