A. Because it’s not easy to remove GIL according to Guido van van Rossumn. It’s an issue and the fact the python community are talking about it means concurrenc

A. Because it’s not easy to remove GIL according to Guido van van Rossumn. It’s an issue and the fact the python community are talking about it means concurrency is an issue. B. Your last comment points to one language and the complexity of adapting it vs ignoring wider argument that there is a greater need for concurrency to add performance than what there was in the 80’s when CPU’s got faster ever year. c. You almost indicate that despite the GIL banks are using python and therefore must be less concerned with concurrency. This is not the case because GIL in no way stops concurrent programming from happening in a single Python process. The only constraint the GIL places on multi-threaded applications is that a single Python process cannot execute multiple threads simultaneously. You can still run multiple threads.