o Most notably, ZEO.ClientStorage (http://www.zope.org/Collectors/Zope/2016)

PersistentMapping was inadvertently pickling volatile attributes (http://www.zope.org/Collectors/Zope/2052).

See http://www.zope.org/Collectors/Zope/2027.

Made new tests ``test_mapping`` conform to the requirements for a ``dict`` initializer in Python 2.3.x.

fixes for ZClasses.  Repaired.

Elsewhere, repaired English in comments.

  tools need to perform minimal logging configuration themselves. Changed
  the zeoup script to do so and thus enable it to emit error messages.

- fixed the API of the pop() method on PersistentDict and PersistentMapping
- no longer try to find pop and popitem on UserDict as all supported
  Python versions have them
- added a test for the default argument of pop()
- added a NEWS.txt entry about pop()

Add descriptions to the <zodb> section keys.

Collector 1900.

send_reply(), return_error():  Stop trying to catch an exception that doesn't
exist, when marshal.encode() raises an exception.  Jeremy simplified the
marshal.encode() half of this about 3 years ago, but apparently forgot to
change ZEO/zrpc/connection.py to match.

transactions for users defined in a non-root acl_users folder. Zope logs a
acl_users path together with a username (separated by a space) and this
previous fix failed to take this into account. Fixed by taking anything after
the last space in the compared path out of the equation.

release from the 3.4 branch.

Collector 1873.

update_from_seq():  If PySequence_Check(seq) returns true,
go on to check for the existence of "iteritems" when deciding
whether the input is or is not "a sequence".  Alas,
PySequence_Check() does return true for PersistentMapping and
PersistentDict instances, so that they couldn't be used as
arguments to BTree/Bucket construction or update().

This is nasty type-sniffing, but it was before too.  There's
no way to make such stuff bulletproof, so I'm settling for
incremental improvement.

storage interfaces.  It would be better to define &
document them, but that takes time, and until time is
available better not to pretend that they're all really
part of "the" storage API.

Also gave it some tests (it was woefully untested).

this helps poor schmucks like me who have to make app-level conflict resolution
work in Products as well. Including INSTANCE_HOME makes sure ZEO can find the
product code in the first place.

simul.py hit NameErrors when startup cache verification
found data in the cache to invalidate.

The cache's loadBefore() implementation called _trace()
incorrectly, passing the tid where the version argument
belonged.

Add missing packaging files, for zpkg use.

There's no possiblity of rollback here, so no need to insist that the
data manager support rollbacks.