We use py-key-value-aio through FastMCP and implemented our own storage backend by subclassing BaseStore. When we updated the library to 0.4.x we noticed that ManagedEntry had moved and we had to update our import. In doing so we realised there is no public path for it.
ManagedEntry appears directly in the signatures of the abstract methods that BaseStore requires external implementors to override. Any custom store implementation must import it. We are currently importing it from key_value.aio._utils, which is a private module.
We use
py-key-value-aiothrough FastMCP and implemented our own storage backend by subclassingBaseStore. When we updated the library to 0.4.x we noticed thatManagedEntryhad moved and we had to update our import. In doing so we realised there is no public path for it.ManagedEntryappears directly in the signatures of the abstract methods thatBaseStorerequires external implementors to override. Any custom store implementation must import it. We are currently importing it fromkey_value.aio._utils, which is a private module.