Closed ailintom closed 5 years ago
I cannot explain this behaviour, but without this addition I am getting non-empty objects when using the function in a multithreading environment (multiprocessing pool or concurrent.futures ThreadPoolExecutor)
I cannot explain this behaviour, but without this addition I am getting non-empty objects when using the function in a multithreading environment (multiprocessing pool or concurrent.futures ThreadPoolExecutor)