The Grok team is happy to announce the release of Grok 0.14!
This release is available on PyPI and a new index of specific versions
of packages used by this release has been frozen at
http://grok.zope.org/releaseinfo/grok-0.14.cfg. This means that new
projects created with grokproject will start using this release right
away.
This release is the first release of Grok that officially supports
Python 2.5 (besides Python 2.4 itself). The main focus of this release
has been a restructuring of Grok, spinning off packages that can now
be used independently in Zope 3 projects as well as in Zope 2 (through
five.grok):
* Spin off of grokcore.view - support for views is now maintained
in this package.
* Spin off of grokcore.security - support for security
declarations is now maintained here
* Spin off of grokcore.formlib - support for zope.formlib based forms
* Spin off of grokui.admin - the admin UI is now distributed
separately, but grokproject automatically will include it when you
create a new grok project.
* the grok.Skin baseclass is now gone and has been simplified with
the grok.skin directive that can be placed on a layer instead.
To upgrade an existing project from 0.13 to 0.14 you have to:
* include grokui.admin explicitly as a dependency in your setup.py
* update the versions.cfg in your project with the version from
http://grok.zope.org/releaseinfo/grok-0.14.cfg
* modify uses of grok.Skin to use the grok.skin directive
For the detailed changelog, see Grok's PyPI entry page.
For detailed upgrade notes, including how to change your application,
see http://grok.zope.org/project/upgrade-notes
For installation instructions and much more on how to use Grok, see
the Grok tutorial: http://grok.zope.org/documentation/book
We hope to hear from you!
If you enjoy Grok, please subscribe to the grok-dev mailing list and
join us in the #grok channel on irc.freenode.net.
http://pypi.python.org/pypi/zc.async
===========
What is it?
===========
The ``zc.async`` package provides **an easy-to-use Python tool that
schedules
work persistently and reliably across multiple processes and machines.**
For instance...
- *Web apps*: maybe your web application lets users request the
creation of a
large PDF, or some other expensive task.
- *Postponed work*: maybe you have a job that needs to be done at a
certain time,
not right now.
- *Parallel processing*: maybe you have a long-running problem that
can be made
to complete faster by splitting it up into discrete parts, each
performed in
parallel, across multiple machines.
- *Serial processing*: maybe you want to decompose and serialize a job.
High-level features include the following:
- easy to use;
- flexible configuration, changeable dynamically in production;
- reliable;
- supports high availability;
- good debugging tools;
- well-tested; and
- friendly to testing.
While developed as part of the Zope project, zc.async can be used
stand-alone.
=================
How does it work?
=================
The system uses the Zope Object Database (ZODB), a transactional,
pickle-based
Python object database, for communication and coordination among
participating
processes.
zc.async participants can each run in their own process, or share a
process
(run in threads) with other code.
The Twisted framework supplies some code (failures and reactor
implementations,
primarily) and some concepts to the package.
======================
Where can I read more?
======================
Quickstarts and in-depth documentation are available in the package
and in
the `new and exciting on-line documentation`_.
.. _`new and exciting on-line documentation`: http://packages.python.org/zc.async/1.5.0/
Thanks for your attention
Gary
