cPickle and copy_reg.safe_constructors

[Greg Chapman]

During its initialization, cPickle (in the init_stuff function) grabs a
reference to copy_reg.safe_constructors; it appears this reference is never
released.  Unfortunately for me, this means that registered constructors are
never released -- I have a constructor which holds a reference to a PyObject
which I would like to have released to ensure that my module is cleaned up
properly.  I can work around the current behavior if necessary, but I was
curious if this behavior should be considered a bug.  Anyone have any idea?

Thanks.

---
Greg Chapman