> Python is a single-threaded language. That’s part of its DNA. If the changes proposed in this PEP go through, that will no longer be the case. So library aut

> Python is a single-threaded language. That’s part of its DNA. If the changes proposed in this PEP go through, that will no longer be the case. So library authors pretty much will have to either update, or see their modules wither the same way they would if they weren't updated as new Python 3.x versions come along. > rather the people who want that should be forced to rewrite their code in a language that is more suitable for the problem they want to solve The vast majority of the Python developer community WANT Python to support true multithreading and being able to solve these problems. We expend inordinate amounts of time and skill trying to make Python work around the GIL, eg. by utilizing multiprocessing. We want Python to stay relevant long-term. In an age of abundant multi-core platforms, and workloads that can utilize them, the GIL is a major obstacle to that desire.