Removing the GIL is a different problem than designing python without a GIL from the start. Preserving C API semantics (in particular reference counting) withou

Removing the GIL is a different problem than designing python without a GIL from the start. Preserving C API semantics (in particular reference counting) without slowing things down is the tricky part. I could be wrong, but I am not aware of any efficient memory management that support multithread well without depending on a 'real' GC