New tests covering corner cases in the storage API, derived from code coverage analysis of DirectoryStorage. FileStorage currently fails checkCreationUndoneGetSerial

Check whether a registered extension method already exists before creating the marshaller attribute. This allows for a smooth migration should a former extension method be promoted to the normal storage interface.

Remove signals file, since the only signal you actually need to use is
for log-file rotation.

A few changes to the rST formatting.

Update the ZEO tests to use the new configuration language.
Remove files from old configuration approach.

Useful for the interim case of ZODB 3.2 and Zope 2.6, where you want
to load from a config file in custom_zodb.py.

When a corrupted record is found, it guesses a location for the next
good transaction header.  If the guessed location happened to have a
'c' character at just the right spot, it would think it was at the end
of the file.

Fix in off-by-one bug in scan() that lead to failure.

Do more sanity checks for invalid transaction headers following a
scan.

Use restore() instead of store() to copy data.  This change should
maximize the chance that the recovered storage is identical except for
the damaged records.

Add tests from the trunk and remove test in testFileStorage.

threads that lead to unreported test failures.

is accessed. This improves some odd unsliceable object TypeErrors which
popped up from inside fsIndex.

happy again.

Reported by Sidnei da Silva.

information to ReadConflictError

(Just hope that the storage is sane :-).

The pack() implementation would leave a corrupted storage behind if
transactions committed while packing.

merge toby_directorystorage_tests_branch. Inhibit tests that use versions when not supported by the storage. Allow a subclass to insert a pause between consecutive packs if needed. DirectoryStorage now passes all the ZODB tests.

for the common case and reducing the impact of any memory leaks associated
with sys._getframe().

Only expose the items attribute of the special dict inside the cache.
Exposing other methods that mutate the dict is dangerous, because of
the ref count games the cache plays.

2.1.