So if recovering a ZODB fails for any reason, it doesn't leave behind
a partial file which may be confused with the recovered file (as it
bears same name).

To give users hints about their origin if cleaning isn't done correctly

But let the caller opening the file closing it

Prep ZODB 5.5.1 release.

Fix KeyError on releasing resources of a Connection when closing the DB.

Use the regular transaction manager wrapped by the thread-transaction
manager so we can call unregisterSynch when close is called from
another thread, typically during database shutdown.

Also, use a daemonic thread so that the test runner doesn't hand
waiting for the thread to die.

Prep 5.5.0 release.

Avoid most calls to time.sleep() in the tests by mocking time.[gm]time

grammar (typo)

Lifted from PR #164.

This happens on Python 3.7, evidinced by Appveyor (https://ci.appveyor.com/project/jimfulton/zodb/build/1.0.176/job/ehutnhnvbm28w5xl) but not travis because we run coverage on travis, and coverage disables refcounts of None.

This also makes us more deterministic. (Based on code I wrote for nti.testing.)

On my machine, this speeds up a sequential test run from 4:08 to 1:30.

We no longer get much benefit from running the layer tests in
parallel, in fact it looks like the overhead actually slows them down
slightly, so stop doing that.

p64 and p64 are faster and create more informative exceptions.

Fixes #216.

Add Python 3.7 support. 

And fix all the deprecations it reports.

Fixes #214 and fixes #215 (well there's one remaining deprecation in 'manuel')

Based on #217 so that all tests pass.

Remove support for 'python setup.py test'. [skip ci]

Fix tests with, and depend on, persistent 4.4.

Skipping CI because tests will fail until #217 is merged.

Fixes #218.

Fixes #213.

This is required to avoid a memory leak on Python 2.7.

See #203.

prefect -> prefetch

(Previously, protocol 2 was used for Python 2.)

  The zodbpickle package provides a `zodbpickle.binary` string type
  that should be used in Python 2 to cause binary strings to be saved
  in a pickle binary format, so they can be loaded correctly in
  Python 3.  Pickle protocol 3 is needed for this to work correctly.

- Object identifiers in persistent references are saved as
  `zodbpickle.binary` strings in Python 2, so that they are loaded
  correctly in Python 3.