The Grok development team is very happy to release Grok 1.0. Grok 1.0 is the culmination of 3 years of work after the start of the Grok project in late 2006. It presents a stable platform for developing powerful, extensible web applications. Grok is the result of years of work by the large Grok development team.
With Grok, simple projects are easy to create, but it is with increasing complexity and reuse that the Grok framework excels.
Grok 1.0 is not the end of Grok development. Since Grok is extensible many powerful new features are being made available as growing collection of extension packages. The Grok development team is also working on a whole range of initiatives to improve Grok even further. The Grok documentation team is also busily working on improving Grok's extensive documentation resources.
Grok is a modern Python-based web framework. Grok is powerful in the hands of an expert developer, as it excels in reuse and extensibility thanks to its use of a component development model. At the same time Grok aims to let less experienced developers be productive immediately, so that the walk up the learning curve is more smooth for them.
Grok lets you store your Python objects easily in the battle-tested ZODB, an object database. Alternatively relational databases are supported with Grok, using the megrok.rdb extension and SQLAlchemy.
Grok is developed in the Zope community and is built with Zope technologies. In particular, Grok builds on the Zope Toolkit, a collection of libraries that make use of a common component development model, the Zope Component Architecture. The Zope community has more than a decade of experience in developing web applications with Python. The Zope Toolkit is the result of this experience,
Grok is WSGI compatible and can therefore be integrated with the wide range of WSGI-based technologies available in the Python world today.
Grok technologies themselves are also available for reuse. This has enabled developers to use them in combination with the Silva and Plone CMS projects, which work with the Zope 2 application server.
Grok 1.0 has the following changes compared to Grok 1.0b2:
- 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.
Grok 1.0b2 has the following changes compared to Grok 1.0a4:
- grokproject layout changed again. we store the database and logfiles under the var directory in the buildout.
- Running the server with debug.ini and the exception middleware in there won't require you to use a different login location for the admin ui. Just going to http://localhost:8080 should give you a login prompt.
This release also contains a number of bugfixes. We are continuing to fix bugs on the way to Grok 1.0.
For installation instructions and much more on how to use Grok, see the Grok tutorial: http://grok.zope.org/doc/current/tutorial.html
Grok 1.0b1 was released a bit prematurely and can be safely ignored.
A significant change to the project structure generated by grokproject has been created too. We recommend you upgrade your projects to the new structure (but be sure to back up important Data.fs files for important ZODBs). Please examine a project generated with the newest version of grokproject and update your project's buildout.cfg accordingly (and help us write better instructions!).
For detailed upgrade notes on this, see http://grok.zope.org/project/upgrade-notes