j2labs/dictshield — Issue #70: Design question: is field deletion avoided on purpose?
Author: atl
Created: 2012-03-05 13:29:10+00:00
State: open

I'm considering hooking dictshield in with an ongoing project, and noticed the lack of `__del__` methods on dictshield.fields.*. Is this a deliberate design decision? Or is it more "haven't needed it yet, why complexify unnecessarily"?

FWIW, I'd like to log destructive accesses to fields (__set__ and __del__ if it appears) for some crude STM.