Update of /cvs-repository/ZODB3
In directory cvs.zope.org:/tmp/cvs-serv22552
Modified Files:
Tag: Zope-2_7-branch
NEWS.txt README.txt setup.py
Log Message:
An internal 3.2.9b1 release.
=== ZODB3/NEWS.txt 1.33.6.81 => 1.33.6.82 ===
--- ZODB3/NEWS.txt:1.33.6.81 Tue Jun 14 16:46:31 2005
+++ ZODB3/NEWS.txt Mon Jun 27 13:10:24 2005
@@ -2,41 +2,47 @@
==========================
Release date: DD-MMM-2005
+Following are dates of internal releases (to support ongoing Zope 2.7
+development) since ZODB 3.2's last public release:
+
+- 3.2.9b1 27-Jun-2005
+
Subtransactions
---------------
-Doing a subtransaction commit erroneously processed invalidations, which could
-lead to an inconsistent view of the database. For example, let T be the
-transaction of which the subtransaction commit was a part. If T read a
-persistent object O's state before the subtransaction commit, did not commit
-new state of its own for O during its subtransaction commit, and O was
-modified before the subtransaction commit by a different transaction, then the
-subtransaction commit processed an invalidation for O, and the state T read
-for O originally was discarded in T. If T went on to access O again, it saw
-the newly committed (by a different transaction) state for O::
-
- o_attr = O.some_attribute
- get_transaction().commit(True)
- assert o_attr == O.some_attribute
+- (3.2.9b1) Doing a subtransaction commit erroneously processed
+ invalidations, which could lead to an inconsistent view of the database.
+ For example, let T be the transaction of which the subtransaction commit
+ was a part. If T read a persistent object O's state before the
+ subtransaction commit, did not commit new state of its own for O during its
+ subtransaction commit, and O was modified before the subtransaction commit
+ by a different transaction, then the subtransaction commit processed an
+ invalidation for O, and the state T read for O originally was discarded in
+ T. If T went on to access O again, it saw the newly committed (by a
+ different transaction) state for O::
+
+ o_attr = O.some_attribute
+ get_transaction().commit(True)
+ assert o_attr == O.some_attribute
-could fail, and despite that T never modified O.
+ could fail, and despite that T never modified O.
FileStorage.UndoSearch
----------------------
-- The ``_readnext()`` method now returns the transaction size as the value
- of the "size" key. Thanks to Dieter Maurer for the patch, from
- http://mail.zope.org/pipermail/zodb-dev/2003-October/006157.html.
- "This is very valuable when you want to spot strange transaction sizes
- via Zope's 'Undo' tab".
+- (3.2.9b1) The ``_readnext()`` method now returns the transaction size as
+ the value of the "size" key. Thanks to Dieter Maurer for the patch, from
+ http://mail.zope.org/pipermail/zodb-dev/2003-October/006157.html. "This is
+ very valuable when you want to spot strange transaction sizes via Zope's
+ 'Undo' tab".
Error reporting
---------------
-- In the unlikely event that ``referencesf()`` reports an unpickling error
- (for example, a corrupt database can cause this), the message it
- produces no longer contains unprintable characters.
+- (3.2.9b1) In the unlikely event that ``referencesf()`` reports an
+ unpickling error (for example, a corrupt database can cause this), the
+ message it produces no longer contains unprintable characters.
What's new in ZODB3 3.2.8?
=== ZODB3/README.txt 1.19.6.23 => 1.19.6.24 ===
--- ZODB3/README.txt:1.19.6.23 Wed Apr 27 15:38:23 2005
+++ ZODB3/README.txt Mon Jun 27 13:10:24 2005
@@ -1,4 +1,4 @@
-ZODB3 3.2.8
+ZODB3 3.2.9
===========
Introduction
@@ -32,15 +32,15 @@
Compatibility
-------------
-ZODB 3.2.8 requires Python 2.3.3 or later. For best results, we recommend
+ZODB 3.2.9 requires Python 2.3.3 or later. For best results, we recommend
using Python 2.3.5. Python 2.4.1 may also be used.
This version of ZODB can be used with Zope 2.7.3 or later, but you must
replace the version of ZODB that comes packaged with Zope. It should be
possible, for example, to install this code into a Zope 2.7 software home.
-The Zope 2.7.3 and 2.7.4 releases are compatible with this version of ZODB.
-Note that Zope 2.7 includes ZEO, so this package should only be needed
+The Zope 2.7.3 through 2.7.7 releases are compatible with this version of
+ZODB. Note that Zope 2.7 includes ZEO, so this package should only be needed
to run a ZEO server.
The ZEO server in ZODB 3.2 is partially compatible with ZODB 3.1. A
@@ -96,7 +96,7 @@
Type "help", "copyright", "credits" or "license" for more information.
>>> import ZODB
>>> ZODB.__version__
- '3.2.8'
+ '3.2.9'
Testing
-------
=== ZODB3/setup.py 1.50.6.31 => 1.50.6.32 ===
--- ZODB3/setup.py:1.50.6.31 Wed Apr 27 14:59:48 2005
+++ ZODB3/setup.py Mon Jun 27 13:10:24 2005
@@ -26,7 +26,7 @@
# Development Status :: 3 - Alpha
classifiers = """\
-Development Status :: 5 - Production/Stable
+Development Status :: 4 - Beta
Intended Audience :: Developers
License :: OSI Approved :: Zope Public License
Programming Language :: Python
@@ -215,7 +215,7 @@
doclines = __doc__.split("\n")
setup(name="ZODB3",
- version="3.2.8",
+ version="3.2.9b1",
maintainer="Zope Corporation",
maintainer_email="zodb-dev at zope.org",
url = "http://www.zope.org/Wikis/ZODB/FrontPage",