Jason Madden

Yes, there are (very) historic reasons for expansive naming, but even Cython is stopping doing that. See https://github.com/matthew-brett/multibuild/commit/02777c9ffaab912062d19952163d59fb68c36be6#diff-c6138a165d27a77acc4f03c58856b4de

Thanks for the report. The warnings here are just about unused static functions. They arise because of the complicated way this package builds its sources by using low-level C macros...

> I'd like to see actual benchmarks showing how this is faster/smaller compared to an OOBTree > (in fact I'd like to see actual benchmarks comparing OOBTree to an LLBTree...

I've been going over these code paths (both the `__getitem__` path, and the paths that involve unghosting objects, both BTrees/buckets and keys). It's not clear to me, by inspection, where...

It's not just BTrees, it's *any* reference to the object. References to persisted objects all include the type so that they can be unghosted: ```pycon >>> from ZODB import DB,...

Is the `music` directory on the Python path (`sys.path`)?

This is somewhat similar to RelStorage's in-memory pickle state cache, which is shared by all Connections of a Storage, but operating on the unpickled data (and then of course copying...

> This cache would be keyed by oid + serial, so it would be orthogonal to MVCC. Ah, I see. It helps that the current laughingly-misnamed "pickle cache" knows what...

I recall issues like this coming up at least once, if not a few times, over in pypi-support. Someone would fork a repository, change the name in `setup.py`, and then...

FWIW, I got the original ``mgzip`` code working on Python 3.12 with this patch, in case its helpful for others running into this issue. When I say "working" I mean...