proposed getting rid of _p_independent for BTree length objects.
The _p_independent is a relic of not having MVCC. While not
all storages have MVCC, the ones that matter do.
BTree length objects are the only objects that use _p_independent.
I propose to drop the _p_independent protocol, which is an
obsolete optimization. Any objections?
For more information about ZODB, see the ZODB Wiki:
ZODB-Dev mailing list - ZODB-Dev@zope.org