Object is unsendable, but is being dropped on another thread

[davidbrochart]

After reading #3688 and #3689, I'm still not sure what to do with an unsendable pyclass. When it is garbage collected from a different thread than the thread it was created in, I get the RuntimeError: ... unsendable, but is being dropped on another thread.
Does it mean that my object is not dropped, and that it would lead to memory leaks?

[davidbrochart]

Oh maybe I didn't get it right: when the object is being garbage collected from a different thread, it will actually not be, and then it will be garbage collected later in its home thread?