I always used to read that, but in practice, threading and multiprocessing modules work just fine for concurrency and parallelism, respectively. What's the issue?
The threading module is restricted by the "Global Interpreter Lock" and cannot run truly concurrently.
My first run-in with this was when I wrote a toy brute-force birthday attack as part of a course I was doing, and realised it was only utilising one core.
The multiprocessing module works as expected, sure.
My first run-in with this was when I wrote a toy brute-force birthday attack as part of a course I was doing, and realised it was only utilising one core.
The multiprocessing module works as expected, sure.