May 31, 2010 - The Zope 3 development team announces the Zope 3.4.1c1 release.
The 3.4.1 is the long awaited next bugfix version of 3.4.0.
For details see the changelog.
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.
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.1c1 ...
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.1c1/controlled-packages.cfg |
[3] | http://download.zope.org/zope3.4/intro.html |
[4] | http://download.zope.org/zope3.4/3.4.1c1/versions.cfg |
[5] | http://pypi.python.org/pypi/zopeproject |
http://download.zope.org/zope3.4/3.4.1c1/controlled-packages.cfg
The classic Zope 3 source release will be made only on request.
The Windows .exe installer will be made only on request.
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 2.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.
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.
Security issue: The traversers defined for IPageletBrowserLayer and IMinimalBrowserLayer was trusted adapters, so the security proxy got removed from each traversed object. Thus all sub-objects were publically accessable, too.
Making this change might BREAK your application! That means if security is not well declared.
Bugfix: use IContentTemplate instead of IPageTemplate which avoids to get the layout template if no IPageTemplate is registered
No changes or information not found.
No changes or information not found.
Bugs fixed:
subclasses to use constructors that expect a different signature. [icemac]
No changes or information not found.
Added the "newest=false" option in the SetUp to prevent upgrade during tests
Bugs Fixed
Bugs Fixed
No changes or information not found.
No changes or information not found.
Initial public release as an individual package.
Zope Application Programming Interface
This package provides a collection of commonly used APIs to make imports simpler.
Mostly, the APIs provided here are imported from elsewhere. A few are provided here.
principals()
The principals method returns the authentication service. If no service is defined, a ComponentLookupError is raised:
>>> from zope.app import zapi >>> zapi.principals() #doctest: +NORMALIZE_WHITESPACE Traceback (most recent call last): ... ComponentLookupError: (<InterfaceClass zope.app.security.interfaces.IAuthentication>, '')
But if we provide an authentication service:
>>> import zope.interface >>> from zope.app.security.interfaces import IAuthentication >>> class FakeAuthenticationUtility: ... zope.interface.implements(IAuthentication) >>> fake = FakeAuthenticationUtility()>>> from zope.app.testing import ztapi >>> ztapi.provideUtility(IAuthentication, fake)
Then we should be able to get the service back when we ask for the principals:
>>> zapi.principals() is fake True
Download
directory. Now it is moved to zope.app.container.browser.tests.
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.
Updated mime-type for .js to be application/javascript.
First stable release as an independent package.
No changes or information not found.
Finished release of zope.deferredimport.
Release 3.4 final, corresponding to Zope 3.4.
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.
Initial release as an independent package
Initial release as an independent package
No changes or information not found.
Removed finally-clause from test to keep Python2.4 happy.
Backport r101467 from trunk.
Fix for https://bugs.launchpad.net/zope3/+bug/98337
Previously, when the Accept-Charset specified a charset that could not encode the result, a system error appeared, now we fall back to UTF-8, as per RFC 2616 section 10.4.7.
Initial release as an independent package
Added BeforeObjectAssignedEvent that is triggered before the object field sets a value.
Public release for completeness of Zope 3.4
No changes or information not found.
Bugs Fixed:
No changes or information not found.
Fixed setup file problems.