The Zope 3 development team is proud to announce Zope 3.1.0 final.
Zope 3 is the next major Zope release and has been written from scratch based
on the latest software design patterns and the experiences of Zope 2.
It is in our opinion that Zope 3.1 is more than ready for production use,
which is why we decided to drop the 'X' for experimental from the name. We
will also continue to work on making the transition between Zope 2 and Zope 3
as smooth as possible. As a first step, Zope 2.8 includes Zope 3 features in
the form of Five.
Now that we have a release that we would like to declare stable next week, we
are looking for translators, who translate Zope 3 into their favorite
language! We are utilizing the Rosetta system from Ubuntu for managing those
translations. If you are not familiar with Rosetta, please send us a mail to
zope3-dev(a)zope.org and we get you set up.
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.1 requires Python 2.3.5 or 2.4.1 to run. You must also have zlib
installed on your system.
Most Important Changes Since 3.0
- New Pluggable Authentication Utility (PAU), which is similar in
philosophy to the Zope 2 PAS. The following features are available in
the in the basic PAU facility:
+ Credentials Plugins: Basic HTTP Auth, Session
+ Authenticator Plugins: Principal Folder, Group Folder
For a detailed description of the pluggable authentication utility,
- Major simplifications to the component architecture:
+ Removal of the concept of a service. All outstanding services were
converted to utilities: Error Reporting, FSSync, Authentication.
+ Site Managers are global and local now; adapters and utilties are
directly registered with the site manager. Now global and local
component registration and lookup behaves very similar.
+ Local registrations can now only have two states: active and
inactive. This simplified the code so much, that 'zope.app.utility',
'zope.app.registration' and 'zope.app.site' were all merged into
+ Implemented menus as utilities. The API also supports sub-menus now.
+ Implemented views as adapters. Skins and layers are now simply
interfaces that the request provides.
- Added an integer-id facility for assigning integer identifiers
- Added basic catalog and index frameworks.
- Added "sources", which are like vocabularies except that they
support very large collections of values that must be
searched, rather than browsed.
- Created a new granting UI that allows advanced searching of
- Implemented a generic user preferences systsem that was designed to be
easily used in TALES expressions and via Python code. Preferences can be
edited via 'http://localhost:8080/++preferences++/'. A demo of the
preferences can be found at::
- ZCML now supports conditional directives using the 'zcml:condition'
attribute. The condition is of the form "verb argument". Two verbs, 'have
feature' and 'installed module' are currently implemented. Features can be
declared via the 'meta:provides' directive.
- Improved API doctool: Code Browser now shows interfaces, text files and
ZCML files; the new Book Module compiles all available doctext files into
an organized book; the new Type Module lets you browser all interface
types and discover interfaces that provide types; views are shown in the
interface details screen; views and adapters are categorized into
specific, extended and generic; user preferences allow you to customize
certain views; 3rd party modules can now be added to the Code Browser.
- Improved I18n-based number and datetime formatting by integrating 'pytz'
for timezone support, implementing all missing format characters, and
reinterpreting the ICU documentation to correctly parse patterns.
- Added '++debug++' traversal adapter that allows you to turn on
debugging flags in 'request.debug'. Currently the following flags
are defined: source, tal, errors.
- Improved logout support.
- Developed a generic 'browser:form' directive. It is pretty much the
same as the 'browser:editform' directive, except that the data is
not stored on some context or adapted context but sent as a dictionary
to special method (by default).
For a complete list of changes see the 'CHANGES.txt' file.
- "Zope 3 Development Web Site":http://dev.zope.org/Zope3
- "Zope 3 Dev Mailing List":http://mail.zope.org/mailman/listinfo/zope3-dev
- "Zope 3 Users Mailing
- IRC Channel: #zope3-dev at irc.freenode.net
Thanks goes to everyone that contributed.
The Zope 3 Development Team
JpyDbg is a Python/Jython IDE/Debugging environnement pluggin for
Version 0.0.13 of JpyDbg has been released.
Check the Home page : http://jpydbg.sourceforge.net for details
blog page : http://jpydbg.blogspot.com/
What's new in V0.013 :
+ IMPROVEMENT: Pylint GUI interface is now available.
+ IMPROVEMENT : Tiny fixes around PYTHONPATH and some unix machine.
Next planified features to come :
- Netbeans IDE plugin module.(More on blog page for this topic)
We are happy to announce that Zope Corporation is now
offering Zope Replication Services (ZRS) in a 30-day
For more information and to download the evaluation
Zope Replication Services (ZRS) increases the reliability
of all Zope enterprise clusters and eliminates the storage
system as a single point of failure.
Sites with high availability requirements must manage
planned and unplanned downtimes. Planned outages include
system maintenance, software / operating system upgrades,
and backups. Unplanned outages include hardware and network
failures. ZRS reduces the downtime associated with these
events by replicating and distributing mission-critical
data storage across distinct physical storages (possibly
in distinct geographic locations).
Should a primary storage fail, a secondary storage can
take its place. Secondary servers can be taken off-line
at any time to undergo repairs, backups, or system
upgrades. When a secondary returns to service, it
automatically resynchronizes with the primary server.
ZRS also improves scalability since secondary servers can
optionally provide additional read-only ZEO connections
while maintaining their replication functions. ZEO client
storages can be configured to connect to any available
secondary, and can be load-balanced among the available
secondary ZRS servers to implement highly-available and
highly-scalable Zope clusters.
ZRS is a 'battle-tested' solution that has provided the
high-availability and disaster recovery solution critical
to large-scale public and internal Zope deployments for
years. Premier brands including the VIACOM radio and
television group, AARP, Community Newspaper Holdings
Inc. (CNHI), and the Joint Intelligence Center, Pacific
(JICPAC) rely on ZRS to ensure reliability and scalability
for their mission-critical Web sites.
The 30-day evaluation release allows organizations to
install and operate ZRS on up to five primary ZODB servers
and on an unlimited number of secondary servers for up to
The current evaluation release (ZRS 1.4.2) is compatible
with Zope versions 2.4 - 2.7. Full releases of ZRS
compatible with Zope 2.8.x and Zope 3.x are also available.
Brian Lloyd brian(a)zope.com
V.P. Engineering 540.361.1716
Zope Corporation http://www.zope.com