The Five team is happy to announce the release of four Five stable
What is Five
Five is a Zope 2 product that allows you to integrate Zope 3
technologies into Zope 2, today. Among others, it allows you to use
Zope 3 interfaces, ZCML-based configuration, adapters, browser pages
(including skins, layers, and resources), automated add and edit forms
based on schemas, object events, as well as Zope 3-style i18n message
We've tried to keep the Five experience as close to Zope 3 as
possible, so this means that what you learn while using Five should
also be applicable to Zope 3, and viceversa.
More information about Five can be found on our website,
About Five 1.2 and 1.3
Five 1.2 and 1.3 are maintenance releases. They are basically
equivalent except that Five 1.2 works with Zope 2.8/X3 3.0 (only) and
1.3 works with Zope 2.9/3.2 (only). Five 1.3 is included in Zope 2.9.
This will be the last release of Five 1.2 I will make as the unofficial
Five release manager. I don't expect the Zope 2.8 line to live on much
longer either. From now on whoever is relying on Five 1.2 will have to
make sure they backport and release fixes themselves. Managing more than
four stable branches is just too much.
About Five 1.4 and 1.5
Five 1.4 and 1.5 are feature releases. They are basically equivalent
except that Five 1.4 works with Zope 2.9/3.2 (only) and 1.5 works with
Zope 2.10/3.3 (only). Five 1.5 is included in Zope 2.10.
Most important features are:
* Added viewlet and content provider support. A big thanks to Alec
Mitchell and his helpers at the Archipelago sprint for making this
* Add zope.formlib support. Please see ``doc/formlib.txt`` for more
information. A big thanks to Jan-Wijbrand Kolman for this.
* Port zope.testbrowser to Zope 2. You can now use
Products.Five.testbrowser.Browser in functional tests. Much thanks
to Brian Sutherland.
* Add python-packages-as-zope-products support which basically allows
for using any python package as a zope product without it having to
live in Products/. Much thanks to Rocky Burt for this.
Zope 2.10 and Five 1.5 are also a big milestone in the convergence of
Zope 2 and Zope 3.
Changes in all releases
* Allow multiple uses of the <class>/<content> directive.
* Fix problem with WebDAV/HEAD requests due to new traversal order.
* Backported the new traversal lookup order from Zope 2.10 (attribute,
adapter, acquired attribute).
Additional changes in Five 1.4.1
* Made the provider directive acquisition wrap the resultant content
provider so that simple providers that need security declarations
(e.g. those that render pagetemplates) can work with the Zope 2
* Added acquisition wrappers to viewlets before updating or rendering.
Additional changes in Five 1.5
* Moved the custom 'provider:' tales expression back into Five. Made
the provider directive acquisition wrap the resultant content provider
so that simple providers that need security declarations (e.g. those
that render pagetemplates) can work with the Zope 2 security
* Added Five.browser.pagetemplatefile.ViewPageTemplateFile as an alias
to ZopeTwoPageTemplateFile and as a Zope 2 correspondence to
* Added tests to make sure that views are not blocked by acquired
* Changed the tests to reflect that defaultView no only works for views
(and not on attributes).
* The FiveSiteManager classes now work again, but are deprecated for the
new zope.component support. There is also a method to migrate
Five.site to zope.component.
About the Zope 3 Base
Five is part of the *Zope 3 Base* project, which aims to offer an
approachable area for developers of Zope 3 related software. More
about the Zope 3 base and its projects can be found on the project
Zope-Announce maillist - Zope-Announce@zope.org
Zope-Announce for Announcements only - no discussions
(Related lists -
Developers: http://mail.zope.org/mailman/listinfo/zope-dev )