sqlitemulti/sqlitemulti/sqlitemulti.py
def delete_thread_id(self, thread_id: int=0) -> None:
        """Instead of using the GC, we can explicitly inform the object a thread closed so it can free the related result queue
        should give better perfs. Can be called from client worker, just before the thread closes."""
        if thread_id == 0:
            thread_id = get_ident()
        with self._result_queues_lock:
            self._result_queues.pop(str(thread_id))
Instead of using the GC, we can explicitly inform the object a thread closed so it can free the related result queue
        should give better perfs. Can be called from client worker, just before the thread closes.
Instead of using the GC, we can explicitly inform the object a thread closed so it can free the related result queue
should give better perfs. Can be called from client worker, just before the thread closes.
Instead of using the GC we can explicitly inform the object a thread closed so it can free the related result queue should give better perfs . Can be called from client worker just before the thread closes .
def delete_thread_id(self, thread_id: int=0) -> None:
        if thread_id == 0:
            thread_id = get_ident()
        with self._result_queues_lock:
            self._result_queues.pop(str(thread_id))
def delete_thread_id ( self , thread_id : int = 0 ) -> None : if thread_id == 0 : thread_id = get_ident ( ) with self . _result_queues_lock : self . _result_queues . pop ( str ( thread_id ) )
Instead of using the GC, we can explicitly inform the object a thread closed so it can free the related result queue
should give better perfs.
Instead of using the GC we can explicitly inform the object a thread closed so it can free the related result queue should give better perfs .
"""Instead of using the GC, we can explicitly inform the object a thread closed so it can free the related result queue
        should give better perfs. Can be called from client worker, just before the thread closes."""
self
thread_id
int