Commit f37f1c70 authored by Tres Seaver's avatar Tres Seaver

Add explicit warnings about Python2-Py3k data incompatibility.

Re-order changelog entries for 4.0.0b1.
parent f2ba643d
...@@ -5,14 +5,27 @@ ...@@ -5,14 +5,27 @@
4.0.0b1 (unreleased) 4.0.0b1 (unreleased)
===================== =====================
- Skip non-unit tests in ``setup.py test``. Use the buildout to run these - Skip non-unit tests in ``setup.py test``. Use the buildout to run tests
tests. requiring "layer" support.
- Added support for Python 3.2 / 3.3.
- Include the filename in the exception message to support debugging in case - Include the filename in the exception message to support debugging in case
``loadBlob`` does not find the file. ``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.
The Python3 support does **not** provide forward- or backward-compatibility
at the data level with Python2, due to changes in the standard library's
pickle 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.
4.0.0a4 (2012-12-17) 4.0.0a4 (2012-12-17)
===================== =====================
......
Markdown is supported
0%
or
You are about to add 0 people to the discussion. Proceed with caution.
Finish editing this message first!
Please register or to comment