Grok

Latest version: v5.1

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

Scan your dependencies

Page 7 of 10

1.1

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

- Add zope.pluggablauth as a dependency.

1.1rc1

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

* Now using grokcore.content for the base content types : Model,
Container and OrderedContainer.

* Lifted the dependency on zope.app.authentication and depend on
zope.password instead.

* Lifted dependencies on deprecate packages zope.app.error and
zope.app.securitypolicy and zope.app.session.

Beside these changes lot of work has been undertaken to remove as much
dependencies on "older" zope.app.* packages as possible from Grok itself
and from the dependencies of Grok. This work is not complete yet.

1.1a2

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

* Updated z3c.recipe.compattest's version and used it for a bin/compattest
that tests grok and all its dependencies.

* Add grok.getApplication() that, similar to grok.getSite() retrieves
the "nearest" enclosing grok.Application object.

* Use zope.container instead of zope.app.container.

* Use zope.catalog instead of zope.app.catalog.

* Use zope.intid instead of zope.app.intid.

* Use zope.keyreference instead of zope.app.keyreference.

1.1a1

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

* This release depends on grokcore.view 1.13a1.

* Add ZTK support (currently ZTK 1.0dev).

* Grokdocs now uses ZTK pinned versions.

* The ``grok.permissions()``, that is used in the ``grok.Role`` component now
accepts references to ``grok.Permission`` class, not just permission ids.
This behaviour is now symetrical to the ``grok.require()`` directive.

* Added an util function, ``create_application``, to create an
application and trigger the correct events during the process.

* Grok now provides an application-centric event to complete the
zope.lifecycle ones. This event, ``ApplicationInitializedEvent``, is
destined to be trigged after the application has been added to a
container. At this particular step, the application is considered
safe for additional content to be created.

* Use grokcore.site and grokcore.annotation instead of builtins
implementations.

* Update the reference to mention ``zope.View``.

* Update the reference to mention direct references to permissions in
``grok.require`` and ``grok.permissions`` in ``grok.Role``.

* Fix documentation bug where virtualenv wasn't explained correctly.

* Remove the ``grok.View`` permission declaration in ``etc/site.zcml.in``,
should have gone in 1.0b2 already

1.0

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

* Removed IReRaiseException adapter registration for IUnauthorized again in
favor of using grokcore.startup's configurable``debug_application_factory``
WSGI application factory function.

* Use newer versions of simplejson and pytz.

See also https://bugs.launchpad.net/grok/+bug/432115

1.0b2

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

See: `upgrade_notes_1.0b2` for special notes on upgrading to this release.

* Revert back to an older version of ``grokui.admin`` that has not seen any
changes related to the ``grok.View`` permission and the
``View``/``CodeView`` split and still has the introspector that is removed
from newer versions.

* ``grokcore.view``, ``grokcore.viewlet`` and ``grokcore.formlib`` and
Grok itself have been updated to undo the ``View``/``CodeView``
split that we had temporarily introduced in the development versions
after Grok 1.0a4. This means the behavior of ``grok.View`` is
unchanged from Grok 1.0a4. Nothing to see here!

* Changed the default permission to ``zope.View`` instead of
``zope.Public``. This means a modification needs to be made to your
``site.zcml`` if you're upgrading an existing Grok-based
project. See the upgrade notes for more information.

See also https://bugs.launchpad.net/grok/+bug/387332

* Bump used zope.app.wsgi version (now: 3.4.2) to support
product-configs in zope.conf files with paster. Fix
https://bugs.launchpad.net/grok/+bug/220440

* Default location for Data.fs and logfiles of grok's sample application is
now ``var/filestorage/`` and ``var/log/`` instead of ``parts/data/``
and ``parts/log/``.

* Bump used `z3c.testsetup` version (now: 0.4). Fix
https://bugs.launchpad.net/grok/+bug/395125

* Bump used ZODB3 version (now: 3.8.3). Fix
https://bugs.launchpad.net/grok/+bug/410703
https://bugs.launchpad.net/grok/+bug/424335

* Added `zope.publisher.interfaces.IReRaiseException` adapter for
IUnauthorized exceptions. Closes
https://bugs.launchpad.net/grok/+bug/332061

* Removed `docutils` and `Pygment` from versions.cfg. Both are pinned
in grokdocs subpackage. Closes
https://bugs.launchpad.net/grok/+bug/340170

* Corrected Content-type; JSON views now report 'application/json'.

* updated zope.publisher dependency to 3.4.8 (fix paster.httpserver
related bugs in XMLRPC, PUT)

* switched buildout to paster based template (like grokproject default)
https://bugs.launchpad.net/grok/+bug/307197

* changed interpreter name from 'python' to 'grokpy'.

* Restructured the upgrade and change documentation so that they now
get generated into separate files by Sphinx

Page 7 of 10

© 2024 Safety CLI Cybersecurity Inc. All Rights Reserved.