I use chests to distribute data. In most cases, the data consumer either doesn't want to change the contents of the chest or doesn't even have the file permissions to. chests write the .keys to disk at close, even if they haven't changed. __delitem__ and __setitem__ both delete files even before a flush, so it might be nice to protect them from programmer errors.
Does this seem useful enough to belong in chest itself, or should I implement this on my end in a subclass or the likes?
I use chests to distribute data. In most cases, the data consumer either doesn't want to change the contents of the chest or doesn't even have the file permissions to. chests write the
.keysto disk at close, even if they haven't changed.__delitem__and__setitem__both delete files even before aflush, so it might be nice to protect them from programmer errors.Does this seem useful enough to belong in chest itself, or should I implement this on my end in a subclass or the likes?