of md5 support to avoid a deprecation warning.  I would love to
reapply 105888 (from the 3.9 branch) when there is an adequate test.
This can be achived through a pretty straightforward conversion of the
existing manual repozo test to an automated test.

Bugs Fixed:
  2 BTree bugs, introduced by a bug fix in 3.9.0c2, sometimes caused
  deletion of keys to be improperly handled, resulting in data being
  available via iteraation but not item access.

generic dostore() method instead of writing a transaction manually.

- make testrepozo.py runnable from a buildout setup
- fix deprecation warning from repozo.py under Python 2.6

hangs under extreme conditions.

  unnecessarily blocked other activity.

  ZEO manages a separate thread for client network IO.  It created
  this thread on import, which caused problems for applications that
  implemented daemon behavior by forking.  Now, the client thread
  isn't created until needed.

usually passed. :(

causing extra pain on windows.

accross revs.

after conflict errors on blobs. :(

servers much easier. This was easier than I expected. I should have
done this a long time ago. :)

----------

- The helper function ZODB.blob.is_blob_record didn't handle having
  None passed to it, but database "delete" records have None for their
  data.

- CVE-2009-2701: Fixed a vulnerability in ZEO storage servers when
  blobs are available. Someone with write access to a ZEO server
  configured to support blobs could read any file on the system
  readable by the server process and remove any file removable by the
  server process.

Fixed to use a separate Random instance.

----------

- BTrees (and TreeSets) kept references to internal keys.
  https://bugs.launchpad.net/zope3/+bug/294788

- BTree Sets and TreeSets don't support the standard set add method.
  (Now either add or the original insert method can be used to add an
  object to a BTree-based set.)