This can happen during DB construction, or after the fact.

zope.testing instead of rolling our own.

Changed the behavior of _ConnectionPool.pop(), to return
None when no connections are available.

Document _p_invalidate().

Most relevant code is much simpler now; there's no longer
a hard limit on the # of connections per DB.  All the
tests pass, but test coverage of the sprawling DB API isn't
very good.

Also gave WeakSet a suitable __contains__ implementation.

If nothing else, it highlights that the transaction package
got put in a wrong place (it and ZODB depend on each other).

Start simplifying the code.

Code cleanups.

Imports normalization.

Now use ZODB.utils.z64 instead of '\0\0\0\0\0\0\0\0' where appropriate.

Connection.root():  Repair error in docstring.

Remove duplicate declaration and definition of py___getstate__.

The tests here have to be run manually for now, so rename
the directory so test.py doesn't complain about it.

Duplicate import removed.

Merge revs 27788 and 27795 from Zope trunk.

See Collector #1350.

ghostify() and unghostify() detect one form of thread insanity
now.  In a debug build, they abort the process if it happens.
In a release build, unghostify() raises SystemError, and
ghostify() ignores it (ghostify() can't raise an exception).

See Collector #1350.

ghostify() and unghostify() detect one form of thread insanity
now.  In a debug build, they abort the process if it happens.
In a release build, unghostify() raises SystemError, and
ghostify() ignores it (ghostify() can't raise an exception).

before I went on vacation a couple weeks ago.

Use proto 1 pickles in ZEO/zrpc/Marshaller.encode().

This rehabilitates the good part of Andreas's change; adds
news; adds comments; and adds more comments about the
sequence of undocumented cPickle gimmicks this relies on.

This rehabilitates the good part of Andreas's change; adds
news; adds comments; and adds more comments about the
sequence of undocumented cPickle gimmicks this relies on.