| Name | grok JSON |
| Version |
5.0
JSON |
| download |
| home_page | https://github.com/zopefoundation/grok |
| Summary | Grok: Now even cavemen can use Zope 3! |
| upload_time | 2024-01-29 12:44:52 |
| maintainer | |
| docs_url | None |
| author | Grok Team |
| requires_python | >=3.7 |
| license | ZPL |
| keywords |
|
| VCS |
 |
| bugtrack_url |
|
| requirements |
No requirements were recorded.
|
| Travis-CI |
No Travis.
|
| coveralls test coverage |
No coveralls.
|
.. image:: https://github.com/zopefoundation/grok/actions/workflows/tests.yml/badge.svg
:target: https://github.com/zopefoundation/grok/actions/workflows/tests.yml
:alt: CI Status
.. image:: https://readthedocs.org/projects/grok/badge/?version=latest
:target: https://grok.readthedocs.io/en/latest/?badge=latest
:alt: Documentation Status
Grok
****
What is grok?
=============
Grok is a smashing web framework based on `Zope Toolkit`_ technology.
.. _`Zope Toolkit`: https://zopetoolkit.readthedocs.io/en/latest/
Grok uses the Component Architecture and builds on Zope concepts like
content objects (models), views, and adapters. Its simplicity lies in
using **convention over configuration** and **sensible defaults** when
wiring components together. That means neither a configuration
language like ZCML nor a lot of repetition are needed to create a web
application with grok.
You can find out much more about Grok at our `website
<https://web.archive.org/web/20221005185405/http://grok.zope.org>`_.
Who is grok?
============
Grok is a friendly caveman from the Stone Age. He has a big club that
he hunts mammoths with. He will also use this club to smash anything
he doesn't like.
"ME GROK SMASH ZCML!"
Getting grok
============
The easiest way to get started with grok is to install the
`grokproject <http://cheeseshop.python.org/pypi/grokproject>`_ package
(e.g. via ``easy_install grokproject``) and then create a new project
area by calling the ``grokproject`` script like so::
$ grokproject MyProject
... many lines of output here
This will create a project area in ``MyProject`` as well as download
and install grok.
You can also get grok from GitHub::
git clone https://github.com/zopefoundation/grok.git
Then follow the instructions in ``INSTALL.rst``.
Grok changes
************
5.0 (2024-01-29)
================
Breaking changes
----------------
- Drop dependency on archived packages:
- ``grokcore.xmlrpc``
- ``grokcore.rest``
- ``grokcore.json``
- ``grokui.admin`` (only used in grokwiki example project)
Fixes
-----
- Fix GrokWiki example app.
- Fix installation documentation.
Changes
-------
- Split ``default.zcml`` off ``configure.zcml`` for easier exclude.
- Split ``dependencies.zcml`` off ``configure.zcml`` for easier reuse.
4.0 (2023-12-19)
================
* Add support for Python 3.11, 3.12.
* Update import paths for lifecycle events.
* Drop support for Python 2.7, 3.5, 3.6.
3.3 (2022-09-01)
================
- Add support for Python 3.9, 3.10.
- Fix deprecation warnings.
3.2 (2020-09-02)
================
- Fix DeprecationWarnings.
- Use zopefoundation/meta/config to harmonize package structure.
- Drop support for Python 3.4, add 3.7 + 3.8.
- Remove some backward compatibility imports.
3.1 (2018-05-09)
================
- Expose ``grok.ignore`` to allow not grokking something in a module.
3.0.1 (2018-01-17)
==================
- Replace the use of ``grok.implements()`` with the ``@grok.implementer()``
directive throughout.
3.0.0 (2018-01-16)
==================
- Python 3 compatibility.
1.15 (2017-05-30)
=================
- Advertise the LazyAnnotation and LazyAnnotationProperty.
1.14.1 (2016-02-15)
===================
- Update tests.
1.14 (2015-06-11)
=================
Note: There are a couple of changes that breaks backward compatibility
with older versions.
- Advertise the ``install_on`` directive from grokcore.site.
- Replace ``ApplicationInitializedEvent`` with
``ApplicationAddedEvent`` from grokcore.site.
- Introduce a new event ``DatabaseCreatedEvent`` which is triggered
only one time when the database is created. For existing application
upgrade to this new version, an event will still be send at the time
of the upgrade.
- Replace ``grok.util.create_application`` with the one from
grokcore.site.util. It is now importable directly from grok.
1.13 (2015-06-04)
=================
- Advertise the ``ObjectEditedEvent`` from grokcore.content.
1.12 (2014-10-20)
=================
- Add ``grok.queryAnnotation()`` and ``grok.deleteAnnotation()`` from
``grokcore.annotation``.
1.11.3 (2013-04-03)
===================
- Fixed application_url() calls to use keyword arguments where the API
defines keyword arguments.
1.11.2 (2013-04-03)
===================
- Fix brown paper bag release where not all resources were included. Again.
1.11.1 (2013-04-03)
===================
- Fix brown paper bag release where not all resources were included.
1.11 (2013-04-03)
=================
- Update ``grok.util.application_url()`` to work correctly with
``grokcore.view.util.url()``.
1.10.3 (2012-05-10)
===================
- Make sure the correct layout is retrieved for layout aware form components
too.
1.10.2 (2012-05-10)
===================
- Import the grokcore.layout.layout directive into the grok namespace too.
1.10.1 (2012-05-02)
===================
- Update version requirements.
1.10 (2012-05-02)
=================
- Split off the Application component and the local_utility directive to
grokcore.site. A backwards compatibility import for Application is left
in place.
- Split off the catalog and indexing components from grok into
grokcore.catalog.
- The permissions() directive, the Permission component and the Role
component moved from grok to grokcore.security. The grok package imports
these component, so they can still be accessed through the grok api.
1.9 (2011-09-06)
================
- Added imports for `querySubscriptions()`, `queryMultiSubscriptions()`,
`queryOrderedSubscriptions()` and `queryOrderedMultiSubscriptions()` functions
that complement the Subscriptions and MultiSubscriptions components.
1.8 (2011-07-14)
================
- Incorporate grokcore.chameleon and have it configured by default.
- Expose the Layout, Page, AddFormPage, EditFormPage, DisplayFormPage and
FormPage components that are brought by grokcore.layout. The grok variants
mixin application_url() and flash() functionality typically found in grok's
viewish components.
- Expose the ExecptionPage, NotFoundPage and UnauthorizedPage component from
grokcore.layout.
- Expose the ContentProvider component from grokcore.view
- Declare the name "index" as default view name for error views.
1.7 (2011-05-26)
================
- Directly depend on zope.app.wsgi and configure it too to have the useful
IResult adapters for (temporary) files registered.
- Import grokcore.component.global_adapter too.
1.6 (2011-04-04)
================
- Fix tests that relied on older versions of zope.testbrowser.
- Added grok.index.Value component.
1.5 (2011-02-14)
================
- Added import for Subscription and MultiSubscription components.
1.4.3 (2011-02-08)
==================
- Fix tests now that error views no longer by default provide ISystemErrorView.
1.4.2 (2011-01-20)
==================
- Should've listed IApplication as part of the grok API too.
1.4.1 (2011-01-20)
==================
- Grok should still provide IApplication in the grok API, even now that it
got moved to grokcore.site.interfaces.
1.4 (2011-01-20)
================
- Define error view baseclasses for IException, INotFound and IUnauthorized
errors: grok.ExceptionView, grok.NotFoundView, grok.UnauthorizedView. Lifts
the indirect dependency on zope.app.http and zope.app.exception.
- Moved the XMLRPC, REST component into separate packages
grokcore.xmlrpc and grokcore.rest. Consequently the custom traverse
components that Grok defined were moved to grokcore.traverser. Grok
the-python-package acts more and more like an import-hub.
- To build the docs we now use `collective.recipe.sphinxbuilder`
instead of our own, early hack (get rid of `grokdocs`
subpackage). Buildout now generates ``grokdocs2html`` and
``grokdocs2pdf`` which should do what you think they do.
- The `IApplication` interface, and getApplication() moved to
``grokcore.site``.
1.3 (2010-11-03)
================
- The `IGrokSecurityView` interface has been to ``grokcore.view``.
- The `make_checker` util function has been moved to ``grokcore.view``.
- The base publisher has been moved to ``grokcore.view`` as an
optional feature : security_publication.
- The JSON component and grokker are now moved to
``grokcore.json``. Grok now depends on this new grokore package.
- Update to latest martian and grokcore.component.
1.2.1 (2010-10-26)
==================
- Grok tutorial example projects updated.
- Documentation updates in preparation for the Grok Toolkit 1.2 release.
- Use zc.buildout-1.5.2.
1.2 (2010-10-13)
================
- No changes were necessary.
1.2a (2010-10-07)
=================
- Grok and the Grok Toolkit now use zc.buildout-1.5.1 that should simplify
Grok's installation story significantly. It is now possible to use a system
Python installation for installing Grok. This obsoletes the ``virtualenv``
requirement.
- Grok and the Grok Toolkit will use the ZTK-1.0 release. Note though that
several package versions are overridden to include bugfix releases.
- Various dependencies have been updated.
- Removed z3c.testsetup-specific test collector from grok.testing. You can
still use z3c.testsetup with grok, but have to declare the dependency in your
project's ``setup.py`` explicitly.
- The grok.View component now uses the grokcore.message package for its
`flash` method.
- Grok test zcml now explicitly sets a defaultView name (to `index.html`).
This has been added since we no longer depend on packages such as
zope.app.zcmlfiles, that used to take care of that configuration step.
- Internationalization of title and description of roles are not lost anymore.
- `create_application` now raises a `KeyError`, in cases of key duplication,
to match the ``zope.container`` behavior. Tests have been adapted accordingly.
- Added `KeyError` error handling to the existing `DuplicationError`, to fit
the ``zope.container`` changes. Tests have been adapted accordingly.
1.1.1 (2010-05-30)
==================
- Make use of the groktoolkit 1.1.1 that includes several bugfix releases
of Grok's dependencies such as:
- zope.password, where the SSHAPasswordManager was fixed.
- zope.publisher, that fixes the long standing XML-RPC "hanging" bug.
- Cleanups in the buildout parts.
- Remove zope.app.twisted.
1.1 (2010-05-18)
================
- Add zope.pluggablauth as a dependency.
1.1rc1 (2010-02-25)
===================
* 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 (2009-12-22)
==================
* 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 (2009-11-17)
==================
* 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 (2009-10-07)
================
* 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 (2009-09-17)
==================
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
1.0b1 (2009-09-14)
==================
* This release happened but never really was fully completed. See the
release notes for 1.0b2 instead.
1.0a4 (2009-05-21)
==================
* Pin grokcore.view to 1.7.
* Import zope.app.container interfaces from their actual definition not from a
re-import.
* JSON views now report a Content-type: text/json. See
https://bugs.launchpad.net/bugs/362902
1.0a3 (2009-04-10)
==================
* Pin grokui.admin to 0.3.2
* Pin grokcore.view to 1.5.
* Pin grokcore.component to 1.6.
1.0a2 (2009-04-08)
==================
* Documentation and doc string updates.
* Pin grokui.admin to 0.3.
* Pin grokcore.view to 1.4.
* Synced versions.cfg with the latest KGS release available at:
http://download.zope.org/zope3.4/3.4.0/versions.cfg
* Expose ``IBeforeTraverseEvent`` for import in the ``grok`` namespace.
1.0a1 (2009-01-08)
==================
See: `upgrade_notes_1.0a1` for special notes on upgrading to this release.
Feature changes
---------------
* Introduced ``grok.interfaces.IGrokSecurityView``, a marker interface
which non-Grok views can use to state that they want to be handled
like regular Grok views by the Grok publisher.
* Expose the ``DirectoryResource`` component from grokcore.view and the
accompanying ``path`` directive.
* Similar to the layers and skins restructuring, the ``grok.RESTProtocol``
baseclass has been removed in favour of a ``grok.restskin(name)`` directive
that can be used on REST layer interfaces. Introduced the IRESTLayer base
interfaces for defining REST layers.
* Besides our extensive existing documentation, we have also started
to add a lot of docstrings to the Grok source code so it becomes
easier to understand.
Bug fixes
---------
* Have GrokForm define an empty actions attribute by default, in order
for "action-less" forms to work easily.
* Allow the grok.layer() directive on JSON components. Closes
https://bugs.launchpad.net/grok/+bug/310558
* Close a bad security hole (also fixed in 0.14.1 and other
releases). See
http://grok.zope.org/blog/security-issue-in-grok-please-upgrade
Restructuring
-------------
* Viewlet-related base classes and helpers have been moved out to a
``grokcore.viewlet`` package which Grok now depends on.
0.14 (2008-09-29)
=================
See: `upgrade_notes_0.14` for special notes on upgrading to this release.
Feature changes
---------------
* Grok now officially supports Python 2.5 and still supports Python 2.4.
* Merged the versions from the zope 3.4c7 KGS (known good set):
http://download.zope.org/zope3.4/versions-3.4.0c7.cfg
So we are now using the latest Zope 3 releases for all Zope packages.
Restructuring
-------------
* The ``grok.admin`` subpackage has been factored out to a separate
package ``grokui.admin``. To have the Grok admin UI available in
your environment, add ``grokui.admin`` to the required packages in
the ``setup.py`` of your package.
* Removed ``grok.Skin`` baseclass in favour of a ``grok.skin(name)``
directive that can be used on layer interfaces. Also removed the
``IGrokLayer`` interface in favour of exposing ``IBrowserRequest``
from the grok package.
* Security-related directives and helpers have been moved out to a
``grokcore.security`` package.
* View-related base classes, directives and grokkers have been moved
out to a ``grokcore.view`` package.
* Form-related base classes and helpers have been moved out to a
``grokcore.formlib`` package.
Bug fixes
---------
* Replace zope.deprecation.tests.warn with grok.testing.warn to:
* Make the signature identical to warnings.warn
* To check for \*.pyc and \*.pyo files.
When zope.deprecation is fixed this warn() function can be removed again.
Makes all the tests pass under Python-2.5.
0.13 (2008-06-23)
=================
See: `upgrade_notes_0.13` for special notes on upgrading to this release.
Restructuring
-------------
* The basic component base classes (``Adapter``, ``MultiAdapter``,
``GlobalUtility``), their grokkers, as well as many of the basic
directives have been factored out to a reusable
``grokcore.component`` package.
* Ported directives to Martian's new directive implementation. As a
result, many helper functions that were available from ``grok.util``
were removed. The functionality is mostly available from the
directives themselves now.
* Refactored class grokkers to make use of Martian's new declarative
way for retrieving directive data from classes, and Martian's new
declarative way to write grokkers. See `upgrade_notes_0.13`
for more information.
Feature changes
---------------
* ``GrokTemplate`` sets up the namespaces for the template by calling
``default_namespace() ``on the view component the template is
associated with. As a result, ``ViewletManagers`` and ``Viewlet``
can now push in the ``viewletmanager`` and ``viewlet`` namespaces
into the template.
* Updated tutorial section about grokproject to fit the latest changes.
* Added ``grok.traversable`` directive for easy traversal to attributes and
methods.
* ``grok.require()`` can refer to subclasses of ``grok.Permission``
directly, instead of their id. This, for one, avoids making typos in
permission ids. Permission components *do* still need the
grok.name() directive for defining the permission's id.
* Added an optional parameter ``data`` to the method ``url()`` that
accepts a dictionary that is then converted to a query string. See
http://grok.zope.org/documentation/how-to/generate-urls-with-the-url-function-in-views/view
* Added an ``OrderedContainer`` component.
* Introduced the new `sphinx`-based documentation engine. See
grokdocs/README.txt for details.
* Merged the versions from the 3.4 KGS (known good set):
http://download.zope.org/zope3.4/versions-3.4.0c1.cfg
We are now using the latest Zope 3 releases for all Zope packages.
See `upgrade_notes_0.13` for more information.
* Added support for easier test setup based on ``z3c.testsetup``. This
is a more stable and more powerful implementation of
``grok.testing.register_all_tests()``. See
http://grok.zope.org/documentation/how-to/tests-with-grok-testing
for details.
* There is now a new ``IContext`` interface available. If you make
your class implement that interface, it (and its subclasses) will be
candidates for being a context in a module (for automatic context
lookup if ``grok.context`` is not present). This relies on a feature
introduced in ``grokcore.component`` 1.1.
* ``grok.Model`` implements ``grok.interfaces.IContext`` now (which is
imported from ``grokcore.component``). ``grok.Container`` now
implements ``grok.interfaces.IContainer``. Traversers and default
views have been set up for these interfaces, so that new
implementations that function as a model or container can be easily
created. Just use ``grok.implements(IContainer)`` or
``grok.implements(IContext)``. This is useful for Grok extensions
that want to implement new content classes.
Bug fixes
---------
* Fix https://bugs.launchpad.net/grok/+bug/226555: the ``url()`` method on
``ViewletManager`` and ``Viewlet`` has been removed now that there's easy
access to the view component the viewlet(manager) is registered for.
* Fix https://bugs.launchpad.net/grok/+bug/231106: Use the
viewletmanager.sort() method for sorting viewlets by using
util.sort_components().
* grok.REST views now have a properly set ``__parent__`` attribute and
will correctly allow acquisition from parent objects, as it's used
by the security policy for acquiring local grants, for example.
* Fix https://bugs.launchpad.net/grok/+bug/229677:
zope.app.securitypolicy egg missing. Now zope.app.securitypolicy
3.4.6 is additionally required by Grok and fetched by buildout.
* Removed first testsetup hack from grok.testing.
* Version 2.1 of z3c.autoinclude contained code that caused Grok to
fail to start on some platforms if the system-supplied Python was
used (at least on some versions of Ubuntu and Debian). Now include
version 2.2 of z3c.autoinclude which should fix this problem. This
fix was also made on Grok 0.12 in its online versions list after
release.
* Port fix of zope.formlib to correctly adapt the context to a FormField's
interface, not the field.
0.12 (2008-04-22)
=================
See: `upgrade_notes_0.12` for special notes on upgrading to this release.
Feature changes
---------------
* The new release needs new version of grokproject, please do::
$ easy_install -U grokproject
* Added testsetup classes in grok.testing to improve easy setup of
unit- and functional tests.
* Add support for viewlets and viewlet managers, ``grok.Viewlet``
and ``grok.ViewletManager``.
* Add a new directive, ``grok.order()``, which can be used to help
sort components. At the time it is not used yet, but we intend to
use it for the viewlets support. Note that this means Grok now
requires Martian 0.9.3 or higher. See ``grok.interfaces`` for more
documentation on this directive.
* Now depend on ``z3c.autoinclude``. This allows the use of the
``<includeDependencies package="."/>`` directive, which automatically loads
up ZCML needed for the dependencies listed in your project's
``setup.py``. The new release of grokproject adds this line
automatically. Upgrade ``grokproject`` to make use of this
functionality in new projects::
$ easy_install -U grokproject
* Classes that end with "-Base" are no longer implicitly considered base
classes. These classes need to have the grok.baseclass() directive added to
them explicitly.
See `upgrade_notes_0.12` for more information.
Bug fixes
---------
* Do not register the publishTraverse and browserDefault methods of the
JSON component as views.
* Methods with names that start with an '_' are not registered as views
for XMLRPC, REST and JSON components.
* Use a configuration action for the registration of the static directory.
* Fix imports from zope.app.securitypolicy.
* Grok does not raise a GrokError anymore when it finds unassociated
templates, but will issue a UserWarning.
* Fix https://bugs.launchpad.net/grok/+bug/161948: grok.testing.grok()
now also loads the ZPT template factories so that unit tests that
need to configure views with ZPT templates continue to work.
* Changed a few remaining references to ``grok.grok`` and
``grok.grok_component`` to their correct equivalents in
``grok.testing``.
* ``grok.testing.grok_component()`` could not be used in a pure
doctest. This needed a bugfix in Martian (since 0.9.2). Add a test
that demonstrates this problem.
* Fix https://bugs.launchpad.net/grok/+bug/162437: grok.Form and its
subclasses did not implement IBrowserView.
* Fix https://bugs.launchpad.net/grok/+bug/185414: grok introspector
was broken for zipped eggs.
* Fix https://bugs.launchpad.net/grok/+bug/125720: server control form
had shutdown as default action, even when entering an admin message.
* Fix https://bugs.launchpad.net/grok/+bug/80403: Fix situation where
a module name is identical to the package name. At least modules
with templates can now have same name as their package.
* Multiple skins and REST protocols could be registered under the same
name, but this is actually a conflict. Now give configuration
conflict error when someone tries this.
* Overriding traversal behavior using the ``traverse()`` method or
``grok.Traverser`` failed in the face of (REST) ``PUT`` and
``DELETE``. XML-RPC also failed when custom traversal was in use.
* Fix https://bugs.launchpad.net/grok/+bug/187590 where config action
discriminators for permission and role registrations were incorrect.
* Permission definitions received the wrong, too high, configure
action priority (not to be confused with grokker priority). In some
cases this caused permissions to be defined later than they were
used. Use a low action priority instead for permissions.
Restructuring
-------------
* Refactor commonalities out of meta.py.
* zope.app.securitypolicy is no longer used. zope.securitypolicy provides
all securitypolicy features used by Grok.
0.11 (2007-11-08)
=================
See: `upgrade_notes_0.11` for special notes on upgrading to this release.
Feature changes
---------------
* Integrated skins and layers: ``grok.layer``, ``grok.IGrokLayer``,
``grok.Skin``.
* Grok now supports hooking in new template languages without much work.
See also doc/minitutorials/template-languages.txt. See Restructuring below
for more techinical info.
* Accessing a template macro via context/@@the_view/the_template is now
deprecated for the standard ZPT story of using
context/@@the_view/macro/the_template.
* There is now a grok.direct() directive that can be used on GlobalUtilities
to mark that the class provides the utility interface directly and need
no instantiation.
* Removed ``grok.define_permission`` in favor of the
``grok.Permission`` component base class. You should now subclass
this base class to define permissions. See also
doc/minitutorials/permissions.txt
* Added the ``grok.Role`` component base class to define roles.
* The admin UI now displays and offers deletion of broken objects.
* Removed support for defining model schemas using an inner class with
the special name ``fields``. This was abandoned in favor the usual
Zope 3 way of defining schemas in interfaces and implementing them
in our Grok models.
* Integrated REST support. See doc/minitutorials/rest.txt for usage
information.
Bug fixes
---------
* Remove zc.recipe.egg, zc.recipe.filestorage, zc.recipe.testrunner,
zc.zope3recipes from version requirements.
* The admin UI now shows interfaces in modules.
* ``handle...`` is not a special function name anymore.
* Views no longer need a custom ``AbsoluteURL`` view to determine
their URL, since each instance now properly gets a ``__name__``
attribute.
* buildout.cfg extends versions.cfg to pin down the versions of the
dependency tree. See also http://grok.zope.org/releaseinfo/readme.html
Restructuring
-------------
* Grokkers now emit configuration actions, much like ZCML directive
handlers do. If you defined custom grokkers,
see `upgrade_notes_0.11` for more information.
* The new pluggable template language support includes some restructuring:
- GrokPageTemplate is now split up into two. BaseTemplate, on which all
templates need to be based, and GrokTemplate, which also provides a
set of methods for easy integration of templating languages.
- All objects based on GrokTemplate are now grokked, instead of having
separate grokkers for each type of template.
- The View is now completely template-language agnostic, which makes it
easy to hook in new page template languages.
- There are now new interfaces (ITemplate and ITemplateFileFactory)
used when you implement support for a new templating language.
* Changed the way grok's functional tests are set up. Instead of each
test case doing its own test setup, it is now done once by the
ftesting layer. This avoids ordering problems when some ftests
would influence the environment of other ftests that were run later
in time.
0.10.2 (2007-10-24)
===================
Bug fixes
---------
* Remove zc.recipe.egg, zc.recipe.filestorage, zc.recipe.testrunner,
zc.zope3recipes from version requirements.
* Require zope.app.error = 3.5.1
0.10.1 (2007-10-10)
===================
Bug fixes
---------
* buildout.cfg extends versions.cfg to pin down the versions of the
dependency tree. This should avoid the situation where we release
Grok, some dependency changes, and Grok breaks as a result. In
conjunction with this we will also be releasing a new version of
grokproject that will use this version infrastructure by default.
For more information about this change, see:
http://grok.zope.org/releaseinfo/readme.html
0.10 (2007-08-21)
=================
Feature changes
---------------
* Integrated admin user interface.
* Configuration using Martian (http://pypi.python.org/pypi/martian).
* Flash message infrastructure included.
* Adjust dependencies for Grok so that grokproject should work on
Windows.
Bug fixes
---------
* A fix in Martian where multiple grok.Model or grok.Container classes
could result in something being found as a context twice.
0.9 series (early 2007 until July 2007)
=======================================
Feature changes
---------------
Grok was released in "continuous release" mode from SVN during this period.
0.1 series (September 2006 until early 2007)
============================================
Feature changes
---------------
Grok was created in September 2006.
Raw data
{
"_id": null,
"home_page": "https://github.com/zopefoundation/grok",
"name": "grok",
"maintainer": "",
"docs_url": null,
"requires_python": ">=3.7",
"maintainer_email": "",
"keywords": "",
"author": "Grok Team",
"author_email": "zope-dev@zope.dev",
"download_url": "https://files.pythonhosted.org/packages/c2/ad/d1d74fe2fd9804ae46916bd53cf9923e364e0b04633f3d8f077e32694bbc/grok-5.0.tar.gz",
"platform": null,
"description": ".. image:: https://github.com/zopefoundation/grok/actions/workflows/tests.yml/badge.svg\n :target: https://github.com/zopefoundation/grok/actions/workflows/tests.yml\n :alt: CI Status\n.. image:: https://readthedocs.org/projects/grok/badge/?version=latest\n :target: https://grok.readthedocs.io/en/latest/?badge=latest\n :alt: Documentation Status\n\nGrok\n****\n\nWhat is grok?\n=============\n\nGrok is a smashing web framework based on `Zope Toolkit`_ technology.\n\n.. _`Zope Toolkit`: https://zopetoolkit.readthedocs.io/en/latest/\n\nGrok uses the Component Architecture and builds on Zope concepts like\ncontent objects (models), views, and adapters. Its simplicity lies in\nusing **convention over configuration** and **sensible defaults** when\nwiring components together. That means neither a configuration\nlanguage like ZCML nor a lot of repetition are needed to create a web\napplication with grok.\n\nYou can find out much more about Grok at our `website\n<https://web.archive.org/web/20221005185405/http://grok.zope.org>`_.\n\nWho is grok?\n============\n\nGrok is a friendly caveman from the Stone Age. He has a big club that\nhe hunts mammoths with. He will also use this club to smash anything\nhe doesn't like.\n\n\"ME GROK SMASH ZCML!\"\n\nGetting grok\n============\n\nThe easiest way to get started with grok is to install the\n`grokproject <http://cheeseshop.python.org/pypi/grokproject>`_ package\n(e.g. via ``easy_install grokproject``) and then create a new project\narea by calling the ``grokproject`` script like so::\n\n $ grokproject MyProject\n ... many lines of output here\n\nThis will create a project area in ``MyProject`` as well as download\nand install grok.\n\nYou can also get grok from GitHub::\n\n git clone https://github.com/zopefoundation/grok.git\n\nThen follow the instructions in ``INSTALL.rst``.\n\nGrok changes\n************\n\n5.0 (2024-01-29)\n================\n\nBreaking changes\n----------------\n\n- Drop dependency on archived packages:\n\n - ``grokcore.xmlrpc``\n\n - ``grokcore.rest``\n\n - ``grokcore.json``\n\n - ``grokui.admin`` (only used in grokwiki example project)\n\nFixes\n-----\n\n- Fix GrokWiki example app.\n\n- Fix installation documentation.\n\nChanges\n-------\n\n- Split ``default.zcml`` off ``configure.zcml`` for easier exclude.\n\n- Split ``dependencies.zcml`` off ``configure.zcml`` for easier reuse.\n\n\n4.0 (2023-12-19)\n================\n\n* Add support for Python 3.11, 3.12.\n\n* Update import paths for lifecycle events.\n\n* Drop support for Python 2.7, 3.5, 3.6.\n\n\n3.3 (2022-09-01)\n================\n\n- Add support for Python 3.9, 3.10.\n\n- Fix deprecation warnings.\n\n\n3.2 (2020-09-02)\n================\n\n- Fix DeprecationWarnings.\n\n- Use zopefoundation/meta/config to harmonize package structure.\n\n- Drop support for Python 3.4, add 3.7 + 3.8.\n\n- Remove some backward compatibility imports.\n\n3.1 (2018-05-09)\n================\n\n- Expose ``grok.ignore`` to allow not grokking something in a module.\n\n3.0.1 (2018-01-17)\n==================\n\n- Replace the use of ``grok.implements()`` with the ``@grok.implementer()``\n directive throughout.\n\n3.0.0 (2018-01-16)\n==================\n\n- Python 3 compatibility.\n\n1.15 (2017-05-30)\n=================\n\n- Advertise the LazyAnnotation and LazyAnnotationProperty.\n\n1.14.1 (2016-02-15)\n===================\n\n- Update tests.\n\n1.14 (2015-06-11)\n=================\n\nNote: There are a couple of changes that breaks backward compatibility\nwith older versions.\n\n- Advertise the ``install_on`` directive from grokcore.site.\n\n- Replace ``ApplicationInitializedEvent`` with\n ``ApplicationAddedEvent`` from grokcore.site.\n\n- Introduce a new event ``DatabaseCreatedEvent`` which is triggered\n only one time when the database is created. For existing application\n upgrade to this new version, an event will still be send at the time\n of the upgrade.\n\n- Replace ``grok.util.create_application`` with the one from\n grokcore.site.util. It is now importable directly from grok.\n\n1.13 (2015-06-04)\n=================\n\n- Advertise the ``ObjectEditedEvent`` from grokcore.content.\n\n1.12 (2014-10-20)\n=================\n\n- Add ``grok.queryAnnotation()`` and ``grok.deleteAnnotation()`` from\n ``grokcore.annotation``.\n\n1.11.3 (2013-04-03)\n===================\n\n- Fixed application_url() calls to use keyword arguments where the API\n defines keyword arguments.\n\n1.11.2 (2013-04-03)\n===================\n\n- Fix brown paper bag release where not all resources were included. Again.\n\n1.11.1 (2013-04-03)\n===================\n\n- Fix brown paper bag release where not all resources were included.\n\n1.11 (2013-04-03)\n=================\n\n- Update ``grok.util.application_url()`` to work correctly with\n ``grokcore.view.util.url()``.\n\n1.10.3 (2012-05-10)\n===================\n\n- Make sure the correct layout is retrieved for layout aware form components\n too.\n\n1.10.2 (2012-05-10)\n===================\n\n- Import the grokcore.layout.layout directive into the grok namespace too.\n\n1.10.1 (2012-05-02)\n===================\n\n- Update version requirements.\n\n1.10 (2012-05-02)\n=================\n\n- Split off the Application component and the local_utility directive to\n grokcore.site. A backwards compatibility import for Application is left\n in place.\n\n- Split off the catalog and indexing components from grok into\n grokcore.catalog.\n\n- The permissions() directive, the Permission component and the Role\n component moved from grok to grokcore.security. The grok package imports\n these component, so they can still be accessed through the grok api.\n\n1.9 (2011-09-06)\n================\n\n- Added imports for `querySubscriptions()`, `queryMultiSubscriptions()`,\n `queryOrderedSubscriptions()` and `queryOrderedMultiSubscriptions()` functions\n that complement the Subscriptions and MultiSubscriptions components.\n\n1.8 (2011-07-14)\n================\n\n- Incorporate grokcore.chameleon and have it configured by default.\n\n- Expose the Layout, Page, AddFormPage, EditFormPage, DisplayFormPage and\n FormPage components that are brought by grokcore.layout. The grok variants\n mixin application_url() and flash() functionality typically found in grok's\n viewish components.\n\n- Expose the ExecptionPage, NotFoundPage and UnauthorizedPage component from\n grokcore.layout.\n\n- Expose the ContentProvider component from grokcore.view\n\n- Declare the name \"index\" as default view name for error views.\n\n1.7 (2011-05-26)\n================\n\n- Directly depend on zope.app.wsgi and configure it too to have the useful\n IResult adapters for (temporary) files registered.\n\n- Import grokcore.component.global_adapter too.\n\n1.6 (2011-04-04)\n================\n\n- Fix tests that relied on older versions of zope.testbrowser.\n\n- Added grok.index.Value component.\n\n1.5 (2011-02-14)\n================\n\n- Added import for Subscription and MultiSubscription components.\n\n1.4.3 (2011-02-08)\n==================\n\n- Fix tests now that error views no longer by default provide ISystemErrorView.\n\n1.4.2 (2011-01-20)\n==================\n\n- Should've listed IApplication as part of the grok API too.\n\n1.4.1 (2011-01-20)\n==================\n\n- Grok should still provide IApplication in the grok API, even now that it\n got moved to grokcore.site.interfaces.\n\n1.4 (2011-01-20)\n================\n\n- Define error view baseclasses for IException, INotFound and IUnauthorized\n errors: grok.ExceptionView, grok.NotFoundView, grok.UnauthorizedView. Lifts\n the indirect dependency on zope.app.http and zope.app.exception.\n\n- Moved the XMLRPC, REST component into separate packages\n grokcore.xmlrpc and grokcore.rest. Consequently the custom traverse\n components that Grok defined were moved to grokcore.traverser. Grok\n the-python-package acts more and more like an import-hub.\n\n- To build the docs we now use `collective.recipe.sphinxbuilder`\n instead of our own, early hack (get rid of `grokdocs`\n subpackage). Buildout now generates ``grokdocs2html`` and\n ``grokdocs2pdf`` which should do what you think they do.\n\n- The `IApplication` interface, and getApplication() moved to\n ``grokcore.site``.\n\n1.3 (2010-11-03)\n================\n\n- The `IGrokSecurityView` interface has been to ``grokcore.view``.\n\n- The `make_checker` util function has been moved to ``grokcore.view``.\n\n- The base publisher has been moved to ``grokcore.view`` as an\n optional feature : security_publication.\n\n- The JSON component and grokker are now moved to\n ``grokcore.json``. Grok now depends on this new grokore package.\n\n- Update to latest martian and grokcore.component.\n\n1.2.1 (2010-10-26)\n==================\n\n- Grok tutorial example projects updated.\n\n- Documentation updates in preparation for the Grok Toolkit 1.2 release.\n\n- Use zc.buildout-1.5.2.\n\n1.2 (2010-10-13)\n================\n\n- No changes were necessary.\n\n1.2a (2010-10-07)\n=================\n\n- Grok and the Grok Toolkit now use zc.buildout-1.5.1 that should simplify\n Grok's installation story significantly. It is now possible to use a system\n Python installation for installing Grok. This obsoletes the ``virtualenv``\n requirement.\n\n- Grok and the Grok Toolkit will use the ZTK-1.0 release. Note though that\n several package versions are overridden to include bugfix releases.\n\n- Various dependencies have been updated.\n\n- Removed z3c.testsetup-specific test collector from grok.testing. You can\n still use z3c.testsetup with grok, but have to declare the dependency in your\n project's ``setup.py`` explicitly.\n\n- The grok.View component now uses the grokcore.message package for its\n `flash` method.\n\n- Grok test zcml now explicitly sets a defaultView name (to `index.html`).\n This has been added since we no longer depend on packages such as\n zope.app.zcmlfiles, that used to take care of that configuration step.\n\n- Internationalization of title and description of roles are not lost anymore.\n\n- `create_application` now raises a `KeyError`, in cases of key duplication,\n to match the ``zope.container`` behavior. Tests have been adapted accordingly.\n\n- Added `KeyError` error handling to the existing `DuplicationError`, to fit\n the ``zope.container`` changes. Tests have been adapted accordingly.\n\n1.1.1 (2010-05-30)\n==================\n\n- Make use of the groktoolkit 1.1.1 that includes several bugfix releases\n of Grok's dependencies such as:\n\n - zope.password, where the SSHAPasswordManager was fixed.\n\n - zope.publisher, that fixes the long standing XML-RPC \"hanging\" bug.\n\n- Cleanups in the buildout parts.\n\n- Remove zope.app.twisted.\n\n1.1 (2010-05-18)\n================\n\n- Add zope.pluggablauth as a dependency.\n\n1.1rc1 (2010-02-25)\n===================\n\n* Now using grokcore.content for the base content types : Model,\n Container and OrderedContainer.\n\n* Lifted the dependency on zope.app.authentication and depend on\n zope.password instead.\n\n* Lifted dependencies on deprecate packages zope.app.error and\n zope.app.securitypolicy and zope.app.session.\n\nBeside these changes lot of work has been undertaken to remove as much\ndependencies on \"older\" zope.app.* packages as possible from Grok itself\nand from the dependencies of Grok. This work is not complete yet.\n\n1.1a2 (2009-12-22)\n==================\n\n* Updated z3c.recipe.compattest's version and used it for a bin/compattest\n that tests grok and all its dependencies.\n\n* Add grok.getApplication() that, similar to grok.getSite() retrieves\n the \"nearest\" enclosing grok.Application object.\n\n* Use zope.container instead of zope.app.container.\n\n* Use zope.catalog instead of zope.app.catalog.\n\n* Use zope.intid instead of zope.app.intid.\n\n* Use zope.keyreference instead of zope.app.keyreference.\n\n1.1a1 (2009-11-17)\n==================\n\n* This release depends on grokcore.view 1.13a1.\n\n* Add ZTK support (currently ZTK 1.0dev).\n\n* Grokdocs now uses ZTK pinned versions.\n\n* The ``grok.permissions()``, that is used in the ``grok.Role`` component now\n accepts references to ``grok.Permission`` class, not just permission ids.\n This behaviour is now symetrical to the ``grok.require()`` directive.\n\n* Added an util function, ``create_application``, to create an\n application and trigger the correct events during the process.\n\n* Grok now provides an application-centric event to complete the\n zope.lifecycle ones. This event, ``ApplicationInitializedEvent``, is\n destined to be trigged after the application has been added to a\n container. At this particular step, the application is considered\n safe for additional content to be created.\n\n* Use grokcore.site and grokcore.annotation instead of builtins\n implementations.\n\n* Update the reference to mention ``zope.View``.\n\n* Update the reference to mention direct references to permissions in\n ``grok.require`` and ``grok.permissions`` in ``grok.Role``.\n\n* Fix documentation bug where virtualenv wasn't explained correctly.\n\n* Remove the ``grok.View`` permission declaration in ``etc/site.zcml.in``,\n should have gone in 1.0b2 already\n\n1.0 (2009-10-07)\n================\n\n* Removed IReRaiseException adapter registration for IUnauthorized again in\n favor of using grokcore.startup's configurable``debug_application_factory``\n WSGI application factory function.\n\n* Use newer versions of simplejson and pytz.\n\n See also https://bugs.launchpad.net/grok/+bug/432115\n\n1.0b2 (2009-09-17)\n==================\n\nSee: `upgrade_notes_1.0b2` for special notes on upgrading to this release.\n\n* Revert back to an older version of ``grokui.admin`` that has not seen any\n changes related to the ``grok.View`` permission and the\n ``View``/``CodeView`` split and still has the introspector that is removed\n from newer versions.\n\n* ``grokcore.view``, ``grokcore.viewlet`` and ``grokcore.formlib`` and\n Grok itself have been updated to undo the ``View``/``CodeView``\n split that we had temporarily introduced in the development versions\n after Grok 1.0a4. This means the behavior of ``grok.View`` is\n unchanged from Grok 1.0a4. Nothing to see here!\n\n* Changed the default permission to ``zope.View`` instead of\n ``zope.Public``. This means a modification needs to be made to your\n ``site.zcml`` if you're upgrading an existing Grok-based\n project. See the upgrade notes for more information.\n\n See also https://bugs.launchpad.net/grok/+bug/387332\n\n* Bump used zope.app.wsgi version (now: 3.4.2) to support\n product-configs in zope.conf files with paster. Fix\n https://bugs.launchpad.net/grok/+bug/220440\n\n* Default location for Data.fs and logfiles of grok's sample application is\n now ``var/filestorage/`` and ``var/log/`` instead of ``parts/data/``\n and ``parts/log/``.\n\n* Bump used `z3c.testsetup` version (now: 0.4). Fix\n https://bugs.launchpad.net/grok/+bug/395125\n\n* Bump used ZODB3 version (now: 3.8.3). Fix\n https://bugs.launchpad.net/grok/+bug/410703\n https://bugs.launchpad.net/grok/+bug/424335\n\n* Added `zope.publisher.interfaces.IReRaiseException` adapter for\n IUnauthorized exceptions. Closes\n https://bugs.launchpad.net/grok/+bug/332061\n\n* Removed `docutils` and `Pygment` from versions.cfg. Both are pinned\n in grokdocs subpackage. Closes\n https://bugs.launchpad.net/grok/+bug/340170\n\n* Corrected Content-type; JSON views now report 'application/json'.\n\n* updated zope.publisher dependency to 3.4.8 (fix paster.httpserver\n related bugs in XMLRPC, PUT)\n\n* switched buildout to paster based template (like grokproject default)\n https://bugs.launchpad.net/grok/+bug/307197\n\n* changed interpreter name from 'python' to 'grokpy'.\n\n* Restructured the upgrade and change documentation so that they now\n get generated into separate files by Sphinx\n\n1.0b1 (2009-09-14)\n==================\n\n* This release happened but never really was fully completed. See the\n release notes for 1.0b2 instead.\n\n1.0a4 (2009-05-21)\n==================\n\n* Pin grokcore.view to 1.7.\n\n* Import zope.app.container interfaces from their actual definition not from a\n re-import.\n\n* JSON views now report a Content-type: text/json. See\n https://bugs.launchpad.net/bugs/362902\n\n\n1.0a3 (2009-04-10)\n==================\n\n* Pin grokui.admin to 0.3.2\n\n* Pin grokcore.view to 1.5.\n\n* Pin grokcore.component to 1.6.\n\n\n1.0a2 (2009-04-08)\n==================\n\n* Documentation and doc string updates.\n\n* Pin grokui.admin to 0.3.\n\n* Pin grokcore.view to 1.4.\n\n* Synced versions.cfg with the latest KGS release available at:\n http://download.zope.org/zope3.4/3.4.0/versions.cfg\n\n* Expose ``IBeforeTraverseEvent`` for import in the ``grok`` namespace.\n\n1.0a1 (2009-01-08)\n==================\n\nSee: `upgrade_notes_1.0a1` for special notes on upgrading to this release.\n\nFeature changes\n---------------\n\n* Introduced ``grok.interfaces.IGrokSecurityView``, a marker interface\n which non-Grok views can use to state that they want to be handled\n like regular Grok views by the Grok publisher.\n\n* Expose the ``DirectoryResource`` component from grokcore.view and the\n accompanying ``path`` directive.\n\n* Similar to the layers and skins restructuring, the ``grok.RESTProtocol``\n baseclass has been removed in favour of a ``grok.restskin(name)`` directive\n that can be used on REST layer interfaces. Introduced the IRESTLayer base\n interfaces for defining REST layers.\n\n* Besides our extensive existing documentation, we have also started\n to add a lot of docstrings to the Grok source code so it becomes\n easier to understand.\n\nBug fixes\n---------\n\n* Have GrokForm define an empty actions attribute by default, in order\n for \"action-less\" forms to work easily.\n\n* Allow the grok.layer() directive on JSON components. Closes\n https://bugs.launchpad.net/grok/+bug/310558\n\n* Close a bad security hole (also fixed in 0.14.1 and other\n releases). See\n http://grok.zope.org/blog/security-issue-in-grok-please-upgrade\n\nRestructuring\n-------------\n\n* Viewlet-related base classes and helpers have been moved out to a\n ``grokcore.viewlet`` package which Grok now depends on.\n\n0.14 (2008-09-29)\n=================\n\nSee: `upgrade_notes_0.14` for special notes on upgrading to this release.\n\nFeature changes\n---------------\n\n* Grok now officially supports Python 2.5 and still supports Python 2.4.\n\n* Merged the versions from the zope 3.4c7 KGS (known good set):\n http://download.zope.org/zope3.4/versions-3.4.0c7.cfg\n So we are now using the latest Zope 3 releases for all Zope packages.\n\nRestructuring\n-------------\n\n* The ``grok.admin`` subpackage has been factored out to a separate\n package ``grokui.admin``. To have the Grok admin UI available in\n your environment, add ``grokui.admin`` to the required packages in\n the ``setup.py`` of your package.\n\n* Removed ``grok.Skin`` baseclass in favour of a ``grok.skin(name)``\n directive that can be used on layer interfaces. Also removed the\n ``IGrokLayer`` interface in favour of exposing ``IBrowserRequest``\n from the grok package.\n\n* Security-related directives and helpers have been moved out to a\n ``grokcore.security`` package.\n\n* View-related base classes, directives and grokkers have been moved\n out to a ``grokcore.view`` package.\n\n* Form-related base classes and helpers have been moved out to a\n ``grokcore.formlib`` package.\n\nBug fixes\n---------\n\n* Replace zope.deprecation.tests.warn with grok.testing.warn to:\n\n * Make the signature identical to warnings.warn\n\n * To check for \\*.pyc and \\*.pyo files.\n\n When zope.deprecation is fixed this warn() function can be removed again.\n Makes all the tests pass under Python-2.5.\n\n0.13 (2008-06-23)\n=================\n\nSee: `upgrade_notes_0.13` for special notes on upgrading to this release.\n\nRestructuring\n-------------\n\n* The basic component base classes (``Adapter``, ``MultiAdapter``,\n ``GlobalUtility``), their grokkers, as well as many of the basic\n directives have been factored out to a reusable\n ``grokcore.component`` package.\n\n* Ported directives to Martian's new directive implementation. As a\n result, many helper functions that were available from ``grok.util``\n were removed. The functionality is mostly available from the\n directives themselves now.\n\n* Refactored class grokkers to make use of Martian's new declarative\n way for retrieving directive data from classes, and Martian's new\n declarative way to write grokkers. See `upgrade_notes_0.13`\n for more information.\n\n\nFeature changes\n---------------\n\n* ``GrokTemplate`` sets up the namespaces for the template by calling\n ``default_namespace() ``on the view component the template is\n associated with. As a result, ``ViewletManagers`` and ``Viewlet``\n can now push in the ``viewletmanager`` and ``viewlet`` namespaces\n into the template.\n\n* Updated tutorial section about grokproject to fit the latest changes.\n\n* Added ``grok.traversable`` directive for easy traversal to attributes and\n methods.\n\n* ``grok.require()`` can refer to subclasses of ``grok.Permission``\n directly, instead of their id. This, for one, avoids making typos in\n permission ids. Permission components *do* still need the\n grok.name() directive for defining the permission's id.\n\n* Added an optional parameter ``data`` to the method ``url()`` that\n accepts a dictionary that is then converted to a query string. See\n\n http://grok.zope.org/documentation/how-to/generate-urls-with-the-url-function-in-views/view\n\n* Added an ``OrderedContainer`` component.\n\n* Introduced the new `sphinx`-based documentation engine. See\n grokdocs/README.txt for details.\n\n* Merged the versions from the 3.4 KGS (known good set):\n http://download.zope.org/zope3.4/versions-3.4.0c1.cfg\n\n We are now using the latest Zope 3 releases for all Zope packages.\n See `upgrade_notes_0.13` for more information.\n\n* Added support for easier test setup based on ``z3c.testsetup``. This\n is a more stable and more powerful implementation of\n ``grok.testing.register_all_tests()``. See\n\n http://grok.zope.org/documentation/how-to/tests-with-grok-testing\n\n for details.\n\n* There is now a new ``IContext`` interface available. If you make\n your class implement that interface, it (and its subclasses) will be\n candidates for being a context in a module (for automatic context\n lookup if ``grok.context`` is not present). This relies on a feature\n introduced in ``grokcore.component`` 1.1.\n\n* ``grok.Model`` implements ``grok.interfaces.IContext`` now (which is\n imported from ``grokcore.component``). ``grok.Container`` now\n implements ``grok.interfaces.IContainer``. Traversers and default\n views have been set up for these interfaces, so that new\n implementations that function as a model or container can be easily\n created. Just use ``grok.implements(IContainer)`` or\n ``grok.implements(IContext)``. This is useful for Grok extensions\n that want to implement new content classes.\n\nBug fixes\n---------\n\n* Fix https://bugs.launchpad.net/grok/+bug/226555: the ``url()`` method on\n ``ViewletManager`` and ``Viewlet`` has been removed now that there's easy\n access to the view component the viewlet(manager) is registered for.\n\n* Fix https://bugs.launchpad.net/grok/+bug/231106: Use the\n viewletmanager.sort() method for sorting viewlets by using\n util.sort_components().\n\n* grok.REST views now have a properly set ``__parent__`` attribute and\n will correctly allow acquisition from parent objects, as it's used\n by the security policy for acquiring local grants, for example.\n\n* Fix https://bugs.launchpad.net/grok/+bug/229677:\n zope.app.securitypolicy egg missing. Now zope.app.securitypolicy\n 3.4.6 is additionally required by Grok and fetched by buildout.\n\n* Removed first testsetup hack from grok.testing.\n\n* Version 2.1 of z3c.autoinclude contained code that caused Grok to\n fail to start on some platforms if the system-supplied Python was\n used (at least on some versions of Ubuntu and Debian). Now include\n version 2.2 of z3c.autoinclude which should fix this problem. This\n fix was also made on Grok 0.12 in its online versions list after\n release.\n\n* Port fix of zope.formlib to correctly adapt the context to a FormField's\n interface, not the field.\n\n0.12 (2008-04-22)\n=================\n\nSee: `upgrade_notes_0.12` for special notes on upgrading to this release.\n\nFeature changes\n---------------\n\n* The new release needs new version of grokproject, please do::\n\n $ easy_install -U grokproject\n\n* Added testsetup classes in grok.testing to improve easy setup of\n unit- and functional tests.\n\n* Add support for viewlets and viewlet managers, ``grok.Viewlet``\n and ``grok.ViewletManager``.\n\n* Add a new directive, ``grok.order()``, which can be used to help\n sort components. At the time it is not used yet, but we intend to\n use it for the viewlets support. Note that this means Grok now\n requires Martian 0.9.3 or higher. See ``grok.interfaces`` for more\n documentation on this directive.\n\n* Now depend on ``z3c.autoinclude``. This allows the use of the\n ``<includeDependencies package=\".\"/>`` directive, which automatically loads\n up ZCML needed for the dependencies listed in your project's\n ``setup.py``. The new release of grokproject adds this line\n automatically. Upgrade ``grokproject`` to make use of this\n functionality in new projects::\n\n $ easy_install -U grokproject\n\n* Classes that end with \"-Base\" are no longer implicitly considered base\n classes. These classes need to have the grok.baseclass() directive added to\n them explicitly.\n\n See `upgrade_notes_0.12` for more information.\n\nBug fixes\n---------\n\n* Do not register the publishTraverse and browserDefault methods of the\n JSON component as views.\n\n* Methods with names that start with an '_' are not registered as views\n for XMLRPC, REST and JSON components.\n\n* Use a configuration action for the registration of the static directory.\n\n* Fix imports from zope.app.securitypolicy.\n\n* Grok does not raise a GrokError anymore when it finds unassociated\n templates, but will issue a UserWarning.\n\n* Fix https://bugs.launchpad.net/grok/+bug/161948: grok.testing.grok()\n now also loads the ZPT template factories so that unit tests that\n need to configure views with ZPT templates continue to work.\n\n* Changed a few remaining references to ``grok.grok`` and\n ``grok.grok_component`` to their correct equivalents in\n ``grok.testing``.\n\n* ``grok.testing.grok_component()`` could not be used in a pure\n doctest. This needed a bugfix in Martian (since 0.9.2). Add a test\n that demonstrates this problem.\n\n* Fix https://bugs.launchpad.net/grok/+bug/162437: grok.Form and its\n subclasses did not implement IBrowserView.\n\n* Fix https://bugs.launchpad.net/grok/+bug/185414: grok introspector\n was broken for zipped eggs.\n\n* Fix https://bugs.launchpad.net/grok/+bug/125720: server control form\n had shutdown as default action, even when entering an admin message.\n\n* Fix https://bugs.launchpad.net/grok/+bug/80403: Fix situation where\n a module name is identical to the package name. At least modules\n with templates can now have same name as their package.\n\n* Multiple skins and REST protocols could be registered under the same\n name, but this is actually a conflict. Now give configuration\n conflict error when someone tries this.\n\n* Overriding traversal behavior using the ``traverse()`` method or\n ``grok.Traverser`` failed in the face of (REST) ``PUT`` and\n ``DELETE``. XML-RPC also failed when custom traversal was in use.\n\n* Fix https://bugs.launchpad.net/grok/+bug/187590 where config action\n discriminators for permission and role registrations were incorrect.\n\n* Permission definitions received the wrong, too high, configure\n action priority (not to be confused with grokker priority). In some\n cases this caused permissions to be defined later than they were\n used. Use a low action priority instead for permissions.\n\nRestructuring\n-------------\n\n* Refactor commonalities out of meta.py.\n\n* zope.app.securitypolicy is no longer used. zope.securitypolicy provides\n all securitypolicy features used by Grok.\n\n0.11 (2007-11-08)\n=================\n\nSee: `upgrade_notes_0.11` for special notes on upgrading to this release.\n\nFeature changes\n---------------\n\n* Integrated skins and layers: ``grok.layer``, ``grok.IGrokLayer``,\n ``grok.Skin``.\n\n* Grok now supports hooking in new template languages without much work.\n See also doc/minitutorials/template-languages.txt. See Restructuring below\n for more techinical info.\n\n* Accessing a template macro via context/@@the_view/the_template is now\n deprecated for the standard ZPT story of using\n context/@@the_view/macro/the_template.\n\n* There is now a grok.direct() directive that can be used on GlobalUtilities\n to mark that the class provides the utility interface directly and need\n no instantiation.\n\n* Removed ``grok.define_permission`` in favor of the\n ``grok.Permission`` component base class. You should now subclass\n this base class to define permissions. See also\n doc/minitutorials/permissions.txt\n\n* Added the ``grok.Role`` component base class to define roles.\n\n* The admin UI now displays and offers deletion of broken objects.\n\n* Removed support for defining model schemas using an inner class with\n the special name ``fields``. This was abandoned in favor the usual\n Zope 3 way of defining schemas in interfaces and implementing them\n in our Grok models.\n\n* Integrated REST support. See doc/minitutorials/rest.txt for usage\n information.\n\nBug fixes\n---------\n\n* Remove zc.recipe.egg, zc.recipe.filestorage, zc.recipe.testrunner,\n zc.zope3recipes from version requirements.\n\n* The admin UI now shows interfaces in modules.\n\n* ``handle...`` is not a special function name anymore.\n\n* Views no longer need a custom ``AbsoluteURL`` view to determine\n their URL, since each instance now properly gets a ``__name__``\n attribute.\n\n* buildout.cfg extends versions.cfg to pin down the versions of the\n dependency tree. See also http://grok.zope.org/releaseinfo/readme.html\n\nRestructuring\n-------------\n\n* Grokkers now emit configuration actions, much like ZCML directive\n handlers do. If you defined custom grokkers,\n see `upgrade_notes_0.11` for more information.\n\n* The new pluggable template language support includes some restructuring:\n\n - GrokPageTemplate is now split up into two. BaseTemplate, on which all\n templates need to be based, and GrokTemplate, which also provides a\n set of methods for easy integration of templating languages.\n\n - All objects based on GrokTemplate are now grokked, instead of having\n separate grokkers for each type of template.\n\n - The View is now completely template-language agnostic, which makes it\n easy to hook in new page template languages.\n\n - There are now new interfaces (ITemplate and ITemplateFileFactory)\n used when you implement support for a new templating language.\n\n* Changed the way grok's functional tests are set up. Instead of each\n test case doing its own test setup, it is now done once by the\n ftesting layer. This avoids ordering problems when some ftests\n would influence the environment of other ftests that were run later\n in time.\n\n0.10.2 (2007-10-24)\n===================\n\nBug fixes\n---------\n\n* Remove zc.recipe.egg, zc.recipe.filestorage, zc.recipe.testrunner,\n zc.zope3recipes from version requirements.\n\n* Require zope.app.error = 3.5.1\n\n0.10.1 (2007-10-10)\n===================\n\nBug fixes\n---------\n\n* buildout.cfg extends versions.cfg to pin down the versions of the\n dependency tree. This should avoid the situation where we release\n Grok, some dependency changes, and Grok breaks as a result. In\n conjunction with this we will also be releasing a new version of\n grokproject that will use this version infrastructure by default.\n\n For more information about this change, see:\n http://grok.zope.org/releaseinfo/readme.html\n\n0.10 (2007-08-21)\n=================\n\nFeature changes\n---------------\n\n* Integrated admin user interface.\n\n* Configuration using Martian (http://pypi.python.org/pypi/martian).\n\n* Flash message infrastructure included.\n\n* Adjust dependencies for Grok so that grokproject should work on\n Windows.\n\nBug fixes\n---------\n\n* A fix in Martian where multiple grok.Model or grok.Container classes\n could result in something being found as a context twice.\n\n0.9 series (early 2007 until July 2007)\n=======================================\n\nFeature changes\n---------------\n\nGrok was released in \"continuous release\" mode from SVN during this period.\n\n0.1 series (September 2006 until early 2007)\n============================================\n\nFeature changes\n---------------\n\nGrok was created in September 2006.\n",
"bugtrack_url": null,
"license": "ZPL",
"summary": "Grok: Now even cavemen can use Zope 3!",
"version": "5.0",
"project_urls": {
"Homepage": "https://github.com/zopefoundation/grok"
},
"split_keywords": [],
"urls": [
{
"comment_text": "",
"digests": {
"blake2b_256": "6c159b1261977fd845884623d37b6949e66beb80dfb49390715503103a6da5bb",
"md5": "7c298a8430ddca2c9182863d41760137",
"sha256": "80c98a778312990124c0ca4bda48041e70d0f5349886fbf9d794a6ac0d2c3789"
},
"downloads": -1,
"filename": "grok-5.0-py3-none-any.whl",
"has_sig": false,
"md5_digest": "7c298a8430ddca2c9182863d41760137",
"packagetype": "bdist_wheel",
"python_version": "py3",
"requires_python": ">=3.7",
"size": 93645,
"upload_time": "2024-01-29T12:44:50",
"upload_time_iso_8601": "2024-01-29T12:44:50.292898Z",
"url": "https://files.pythonhosted.org/packages/6c/15/9b1261977fd845884623d37b6949e66beb80dfb49390715503103a6da5bb/grok-5.0-py3-none-any.whl",
"yanked": false,
"yanked_reason": null
},
{
"comment_text": "",
"digests": {
"blake2b_256": "c2add1d74fe2fd9804ae46916bd53cf9923e364e0b04633f3d8f077e32694bbc",
"md5": "5e9959419ecef65c8a2cf674ff84ea82",
"sha256": "c111bc730dd624baad6de72be72413f2a57c7ca3e8607483e129591cb68f5d46"
},
"downloads": -1,
"filename": "grok-5.0.tar.gz",
"has_sig": false,
"md5_digest": "5e9959419ecef65c8a2cf674ff84ea82",
"packagetype": "sdist",
"python_version": "source",
"requires_python": ">=3.7",
"size": 95859,
"upload_time": "2024-01-29T12:44:52",
"upload_time_iso_8601": "2024-01-29T12:44:52.642530Z",
"url": "https://files.pythonhosted.org/packages/c2/ad/d1d74fe2fd9804ae46916bd53cf9923e364e0b04633f3d8f077e32694bbc/grok-5.0.tar.gz",
"yanked": false,
"yanked_reason": null
}
],
"upload_time": "2024-01-29 12:44:52",
"github": true,
"gitlab": false,
"bitbucket": false,
"codeberg": false,
"github_user": "zopefoundation",
"github_project": "grok",
"travis_ci": false,
"coveralls": false,
"github_actions": true,
"tox": true,
"lcname": "grok"
}
