Grok 1.3 is a feature release of Grok based on the Zope Toolkit 1.1c1.
The Grok development team is happy to announce the Grok 1.3 release!
Where the previous release was mostly about slimming down the dependency hierarchy of packages that comprises Grok, this release brings several important changes in functionality typically found Grok-based applications.
Grok 1.3 is based on the Zope Toolkit 1.1c1 release!
Since the ZTK 1.1 release drops Python-2.4 support and gains Python 2.7 support, it was able to update quite a number of packages, most notably the ZODB. Grok does currently not need to override any version of packages defined in the ZTK!
The list of Grok specific package version can be found here:
To upgrade existing project you might find the upgrade notes helpful, to be found here:
Amongst other changes, Grok 1.3 brings:
- The long awaited support for the most recent martian version.
- The long awaited merge of the template registry refactoring. This should result in considerable less spurious warnings concerning unassociated templates.
- Integration of the Fanstatic library and WSGI components. From the Fanstatic website:
The "static" directory functionality in Grok based projects is now based on Fanstatic and the compatibility layer provided by zope.fanstatic.
- Removal of the automatic test discovery and registration that was provided by the z3c.testsetup package. For newly created projects, the grokproject tool will layout examples of setting up test suites. Note that this is a first step in the way towards more drastic improvements in regards to test discovery and running tests.
Other important notes:
- The updated grokproject tool will not be able to build new project based on Grok version < 1.3.
- Besides working on code, the Grok community is also working on improving the documentation, both the "official" documentation and the "community"-driven efforts. This is quite an undertaking and not yet finished.
We realize this release will again bring quite some structural changes that might affect your projects in some way. Please let us know when you run into problems upgrading your projects on the grok-dev mailinglist or on the #grok IRC channel. We will try to help and it will also help us, the Grok developers, by fixing bugs and other issues.