All Versions
72
Latest Version
Avg Release Cycle
79 days
Latest Release
1414 days ago

Changelog History
Page 4

  • v4.1.0 Changes

    January 11, 2015
    • 🛠 Fix registration of custom logging level names ("BLATHER", "TRACE").

    We have been registering them in the wrong order since 2004. Before Python 3.4, the stdlib logging module masked the error by registering them in both directions.

    • ➕ Add support for Python 3.4.

  • v4.0.1 Changes

    July 13, 2014

    • 🛠 Fix POSKeyError during transaction.commit when after savepoint.rollback. See https://github.com/zopefoundation/ZODB/issues/16

    • Ensure that the pickler used in PyPy always has a persistent_id attribute (inst_persistent_id is not present on the pure-Python pickler). (PR #17)

    • 👍 Provide better error reporting when trying to load an object on a closed connection.

  • v4.0.0 Changes

    August 18, 2013

    🚀 Finally released.

  • v4.0.0.b3 Changes

    June 11, 2013

    • Switch to using non-backward-compatible pickles (protocol 3, without storing bytes as strings) under Python 3. Updated the magic number for file-storage files under Python3 to indicate the incompatibility.

    • 🛠 Fixed: A UnicodeDecodeError could happen for non-ASCII OIDs when using bushy blob layout.

  • v4.0.0.b2 Changes

    May 14, 2013

    • ✅ Extended the filename renormalizer used for blob doctests to support the filenames used by ZEO in non-shared mode.

    • ➕ Added url parameter to setup() (PyPI says it is required).

  • v4.0.0.b1 Changes

    May 10, 2013

    • 🏗 Skipped non-unit tests in setup.py test. Use the buildout to run tests requiring "layer" support.

    • 👻 Included the filename in the exception message to support debugging in case loadBlob does not find the file.

    • ➕ Added support for Python 3.2 / 3.3.

    .. note::

    ZODB 4.0.x is supported on Python 3.x for new applications only. Due to changes in the standard library's pickle support, the Python3 support does not provide forward- or backward-compatibility at the data level with Python2. A future version of ZODB may add such support.

    Applications which need migrate data from Python2 to Python3 should plan to script this migration using separte databases, e.g. via a "dump-and-reload" approach, or by providing explicit fix-ups of the pickled values as transactions are copied between storages.

  • v4.0.0.a4 Changes

    December 17, 2012
    • Enforced usage of bytes for _p_serial of persistent objects (fixes compatibility with recent persistent releases).

  • v4.0.0.a3 Changes

    December 01, 2012
    • 🛠 Fixed: An elaborate test for trvial logic corrupted module state in a way that made other tests fail spuriously.

  • v4.0.0.a2 Changes

    November 13, 2012

    🐛 Bugs Fixed

    • An unneeded left-over setting in setup.py caused installation with pip to fail.

  • v4.0.0.a1 Changes

    November 07, 2012

    🆕 New Features

    • 🚀 The persistent and BTrees packages are now released as separate distributions, on which ZODB now depends.

    • ZODB no longer depends on zope.event. It now uses ZODB.event, which uses zope.event if it is installed. You can override ZODB.event.notify to provide your own event handling, although zope.event is recommended.

    • BTrees allowed object keys with insane comparison. (Comparison inherited from object, which compares based on in-process address.) Now BTrees raise TypeError if an attempt is made to save a key with comparison inherited from object. (This doesn't apply to old-style class instances.)

    🐛 Bugs Fixed

    • Ensured that the export file and index file created by repozo share the same timestamp.

    https://bugs.launchpad.net/zodb/+bug/993350

    • 📌 Pinned the transaction and manuel dependencies to Python 2.5- compatible versions when installing under Python 2.5.

    .. note:: Please see https://github.com/zopefoundation/ZODB/blob/master/HISTORY.rst for older versions of ZODB.