January 29, 2009 - The Zope 3 development team announces the Zope 3.4.0 release.
After 2 years of development, the Zope Foundation and the larger Zope community is proud to announce the release of Zope 3.4.0.
The focus of the Zope 3.4 development effort has been the conversion from a monolithic source tree, to a set of many small packages (eggs), that can be used independently of each other. The core has been further stabilized through numerous bug fixes, and many new add-on packages have been developed to provide a richer development experience.
With this release also comes a renewed commitment to a short and reliable release cycle of 6 months.
Zope 3 is now fully converted to an egg-based system. While some work still remains, it integrates very well with the rest of the Python community. The conversion to egg-based packaging also enables other Python developers to only have to use small bits and pieces of the complete Zope software system. The conversion means that Zope 3 developers do not use the classic Zope 3 tar-ball release anymore. However, for your convenience, Zope 3 developers will provide the classic Zope 3 tar ball releases for at least the 3.4 series and probably for 3.5 as well.
So how are Zope 3 applications built using only eggs?
The known good set -- or in short KGS -- is a configuration of packages and their versions that are known to work well together. The compatibility is frequently verified by running over twelve thousand tests on a daily basis [1]. The KGS is tested against Python 2.4 and 2.5 on the 32- and 64-bit platforms. The list of controlled packages and their versions for Zope 3.4 can be found at the Zope 3 KGS site [2].
The KGS can be used in several ways [3]. The most common way is to "nail" the versions by downloading the version configuration file [4] and insert them as follows in your buildout configuration:
[buildout] versions = versions ... [versions] zope.interface = 3.4.0 ...
To start building a project using a common setup, a package called zopeproject can be used to quickly setup the boilerplate for the project. Ample documentation is provided at the zopeproject home page [5]. zopeproject uses Paste or ZDaemon to create a working server. The following commands get you started:
$ easy_install zopeproject $ zopeproject HelloWorld $ cd HelloWorld $ bin/helloworld-ctl foreground
At this point, there is no demo package demonstrating a simple Zope 3 application setup. However, the z3c.formdemo package can be used as a fairly minimal setup. To get started with it, enter the following:
$ svn co svn://svn.zope.org/repos/main/z3c.formdemo/tags/1.5.3 formdemo $ cd formdemo $ python bootstrap.py $ ./bin/buildout -v $ ./bin/demo fg
[1] | http://zope3.pov.lt/buildbot |
[2] | http://download.zope.org/zope3.4/3.4.0/controlled-packages.cfg |
[3] | http://download.zope.org/zope3.4/intro.html |
[4] | http://download.zope.org/zope3.4/3.4.0/versions.cfg |
[5] | http://pypi.python.org/pypi/zopeproject |
http://download.zope.org/zope3.4/3.4.0/controlled-packages.cfg
Installation instructions for both Windows and Un*x/Linux are now available in the top level README.txt file of the distribution. The binary installer is recommended for Windows.
Zope 3.4 requires Python 2.4 or 3.5 to run. You must also have zlib installed on your system.
#zope3-dev at irc.freenode.net
Zope 3 is a web application server that continues to build on the heritage of Zope. It was rewritten from scratch based on the latest software design patterns and the experiences of Zope 2.
The component architecture is the very core of Zope 3 that allows developers to create flexible and powerful web applications.
Zope 3 is not upwards compatible with Zope 2. This means you cannot run Zope 2 applications in Zope 3.
We continue to work on the transition from Zope 2 to Zope 3 by making Zope 2 use more and more of the Zope 3 infrastructure. This means that new code written in Zope 2 can benefit from Zope 3 technology. Also, with care, code can be written that works in both Zope 3 and Zope 2. This allows a Zope 2 application to slowly evolve towards Zope 3. Unchanged Zope 2 applications are never expected to work in Zope 3, however.
The Zope Foundation, based in Fredricksburg, Virginia, is a not-for-profit organisation that provides support for the Zope community and the Zope platform and its associated software. Its community includes the open source community of contributers as well as the community of businesses and organizations that use Zope.
No changes or information not found.
No changes or information not found.
No changes or information not found.
Bugs fixed
Other changes
No changes or information not found.
No changes or information not found.
No changes or information not found.
No changes or information not found.
Feature: There is now a special unique prefix generator that uses z3c.form's new createCSSId() function to generate css selectable prefixes for ajax forms.
Feature: There is now a viewlet manager already registered with all the viewlets necessary to use z3c.formjs. You can now just do:
<script tal:replace="structure provider:z3c.formjs.interfaces.IDynamicJavaScript"> </script>
Feature: When AJAX handlers return complex data structures (dictionaries, lists and tuples), the data is automatically converted into JSON format before delivery.
Restructure: Make package run on latest z3c.form 1.9.0 release.
Bug: Widgets that were being updated multiple times were generating duplicate javascript event subscriptions. This is now fixed.
No changes or information not found.
No changes or information not found.
No changes or information not found.
Bugs fixed:
New features:
Bugs fixed:
???
No changes or information not found.
Added the "newest=false" option in the SetUp to prevent upgrade during tests
Fixed bug: The zope.conf site-definition option could not be overridden.
Final release with Windows support.
No changes or information not found.
No changes or information not found.
Include information about which attributes changed in the IObjectModifiedEvent after upload.
This fixes https://bugs.launchpad.net/zope3/+bug/98483.
Before 3.4
This package was part of the Zope 3 distribution and did not have its own CHANGES.txt. For earlier changes please refer to either our subversion log or the CHANGES.txt of earlier Zope 3 releases.
No further changes since 3.4.0b2.
Initial public release as an individual package.
directory. Now it is moved to zope.app.container.browser.tests.
Initial release as an independent package
Initial release as an independent package
No further changes since 3.4.0a1.
Before 3.4.0
This package was part of the Zope 3 distribution and did not have its own CHANGES.txt. For earlier changes please refer to either our subversion log or the CHANGES.txt of earlier Zope 3 releases.
First stable release as an independent package.
No further changes since 3.4.0a1.
No changes or information not found.
Finished release of zope.deferredimport.
Release 3.4 final, corresponding to Zope 3.4.
No changes or information not found.
No further changes since 3.4.0a1.
No changes or information not found.
No further changes since 3.4.0a1.
No changes or information not found.
Fixed bug in package metadata (wrong homepage URL).
Fixed a setup bug that prevented installation from source on systems without setuptools.
Final release for 3.4.0.
Initial release as an independent package
No changes or information not found.
No changes since 3.4.1b2.
Initial release as an independent package
Added BeforeObjectAssignedEvent that is triggered before the object field sets a value.
No changes since 3.4.0a1.
Made WSGI server really WSGI-compliant by adding variables to the environment that are required by the spec.
No changes or information not found.
Public release for completeness of Zope 3.4
No changes or information not found.
Bugs Fixed:
Bugs Fixed:
Bugs Fixed:
Bugs Fixed:
Bugs Fixed:
New Features
Bugs Fixed:
No changes or information not found.
No further changes since 3.4.0a1.
Fixed setup file problems.