Commit f9af3f09 authored by JeanMichel FRANCOIS's avatar JeanMichel FRANCOIS

fix tests and improve changelog

parent 69c18075
...@@ -5,8 +5,8 @@ ...@@ -5,8 +5,8 @@
4.0.0.dev (unreleased) 4.0.0.dev (unreleased)
====================== ======================
- improve logging when blob is not found: include the filename requested - Include the filename in the exception message to support debugging in case
which doesn't exists loadBlob does not find the file.
4.0.0a4 (2012-12-17) 4.0.0a4 (2012-12-17)
===================== =====================
...@@ -315,7 +315,7 @@ Bugs fixed ...@@ -315,7 +315,7 @@ Bugs fixed
their subconnections weren't cleaned up properly. their subconnections weren't cleaned up properly.
- ZEO didn't work with IPv6 addrsses. - ZEO didn't work with IPv6 addrsses.
Added IPv6 support contributed by Martin v. Löwis. Added IPv6 support contributed by Martin v. L�wis.
- A file storage bug could cause ZEO clients to have incorrect - A file storage bug could cause ZEO clients to have incorrect
information about current object revisions after reconnecting to a information about current object revisions after reconnecting to a
......
...@@ -394,7 +394,7 @@ And we shouldn't be able to read the data that we saved: ...@@ -394,7 +394,7 @@ And we shouldn't be able to read the data that we saved:
>>> blob_storage.loadBlob(blob._p_oid, s1) >>> blob_storage.loadBlob(blob._p_oid, s1)
Traceback (most recent call last): Traceback (most recent call last):
... ...
POSKeyError: 'No blob file' POSKeyError: 'No blob file at ...'
Of course the old data should be unaffected: Of course the old data should be unaffected:
...@@ -411,7 +411,7 @@ Similarly, the new object wasn't added to the storage: ...@@ -411,7 +411,7 @@ Similarly, the new object wasn't added to the storage:
>>> blob_storage.loadBlob(blob._p_oid, s2) >>> blob_storage.loadBlob(blob._p_oid, s2)
Traceback (most recent call last): Traceback (most recent call last):
... ...
POSKeyError: 'No blob file' POSKeyError: 'No blob file at ...'
.. clean up .. clean up
......
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