> Naiive question: Who needs No-GIL when we have asyncio and multiprocessing packages ? 1. Because asyncio is completely useless when the problem is CPU bound,

> Naiive question: Who needs No-GIL when we have asyncio and multiprocessing packages ? 1. Because asyncio is completely useless when the problem is CPU bound, as the event loop still runs only on a single core. As the name implies, it is really only helpful when problems are IO bound. 2. Because sharing data between multiple processes is a giant PITA. Controlling data AND orchestrating processes is an even bigger pain. 3. Processes are expensive, and due to the aforementioned pain of sharing data, greenlets are not really a viable solutions.