We are happy to announce that ZODB 3.2 release candidate 1 has been
released. You can find it at the usual place:
This release contains a few bug fixes since the ZODB 3.2b3 release last
week. If no major bugs are found in the release candidate, we will make
the final release next week with identical code. If there are bugs, we
will do another release candidate next week.
What is ZODB? It is the Zope Object Database. It provides an
object-oriented database for Python that provides a high-degree of
transparency. Applications can take advantage of object database
features with few, if any, changes to application logic. ZODB includes
features such as a pluggable storage interface, rich transaction
support, and undo.
ZODB 3.2 has a number of new features and improvements over ZODB 3.1:
- improve performance and stability of ZEO
- new ZEO authentication protocol
- new configuration language, ZConfig, for databases, storages,
and ZEO servers
- many bug fixes
- improved documentation
- new daemon tools
The most recent changes from the NEWS.txt file are included below.
-- Jeremy Hylton <http://www.python.org/~jeremy/>
What's new in ZODB3 3.2 release candidate 1
Release date: 01-Oct-2003
Added a summary to the Doc directory. There are several new documents
in the 3.2 release, including "Using zdctl and zdrun to manage server
processes" and "Running a ZEO Server HOWTO."
Fixed ZEO's protocol negotiation mechanism so that a client ZODB 3.1
can talk to a ZODB 3.2 server.
Fixed a memory leak in the ZEO server. The server was leaking a few
KB of memory per connection.
Fixed a memory leak in the ZODB object cache (cPickleCache). The
cache did not release two references to its Connection, causing a
large cycle of objects to leak when a database was closed.
Fixed a bug in the ZEO code that caused it to leak socket objects on
Windows. Specifically, fix the trigger mechanism so that both sockets
created for a trigger are closed.
Fixed a bug in the ZEO storage server that caused it to leave temp
files behind. The CommitLog class contains a temp file, but it was
not closing the file.
Changed the order of setuid() and setgid() calls in zdrun, so that
setgid() is called first.
Added a timeout to the ZEO test suite that prevents hangs. The test
suite creates ZEO servers with randomly assigned ports. If the port
happens to be in use, the test suite would hang because the ZEO client
would never stop trying to connect. The fix will cause the test to
fail after a minute, but should prevent the test runner from hanging.
The logging package was updated to include the latest version of the
logging package from Python CVS. Note that this package is only
installed for Python 2.2. In later versions of Python, it is
available in the Python standard library.
The ZEO1 directory was removed from the source distribution. ZEO1 is
not supported, and we never intended to include it in the release.
[Please repost to local Python mailing lists.]
Want to share your expertise? PyCon DC 2004 is looking for proposals to
fill the formal presentation tracks.
PyCon DC 2003 had a broad range of presentations, from reports on
academic and commercial projects to tutorials and case studies, and we
hope to extend that range this year. As long as the presentation is
interesting and potentially useful to the Python community, it will be
considered for inclusion in the program.
The proposal deadline is December 1; the proposal submission system
should be up by mid-October. We'll send out another notice with more
info when the submission system goes live.
Proposals should be 250-1000 words in text (plain or reST) or HTML. You
may request either thirty or sixty minutes for your timeslot. Proposals
will be accepted or rejected by January 1, 2004. If your proposal is
accepted, you may include a companion paper for publication on the PyCon
If you don't want to make a formal presentation, there will be a
significant amount of Open Space to allow for informal and
spur-of-the-moment presentations for which no formal submission is
required. There will also be several Lightning Talk sessions (five
minutes or less).
For more information, see http://www.python.org/pycon/dc2004/cfp.html
PyCon is a community-oriented conference targeting developers (both those
using Python and those working on the Python project). It gives you
opportunities to learn about significant advances in the Python
development community, to participate in a programming sprint with some
of the leading minds in the Open Source community, and to meet fellow
developers from around the world. The organizers work to make the
conference affordable and accessible to all.
DC 2004 will be held March 24-26, 2004 in Washington, D.C. The keynote
speaker is Mitch Kapor of the Open Source Applications Foundation
(http://www.osafoundation.org/). There will be a four-day development
sprint before the conference.
We're looking for volunteers to help run PyCon. If you're interested,
subscribe to http://mail.python.org/mailman/listinfo/pycon-organizers
Don't miss any PyCon announcements! Subscribe to
You can discuss PyCon with other interested people by subscribing to
The central resource for PyCon DC 2004 is
Aahz (aahz(a)pythoncraft.com) <*> http://www.pythoncraft.com/
"It is easier to optimize correct code than to correct optimized code."
I've just finished a little patch to logging.handlers to send logging
events notification as both jabber and spread messages.
It's rather untested, but perhaps it's already useful.
You'll find it at http://pyhacks.suddenthinks.com/
Any comment will be appreciated, as usual.
Gian Paolo Ciceri Via G.Marconi 5 - 22036 ERBA CO ITALY
mobile : ++39 340 7218101
: ++39 329 8103661
eMail : gp.ciceri(a)acm.org,
ICQ # : 94620118
jabber : gp.ciceri(a)jabber.com