ThreadPool instead of multiprocessing.Pool
Opened this issue · 0 comments
julkiewicz commented
Would there be any problems with using ThreadPool instead of multiprocessing.Pool in the library?
I created a patch that performs the switch however I would like to understand whether this change doesn't cause any thread-safety problems. From what I can see requests library is thread-safe. Are there any shared resources between different "jobs" executed inside the pool?