> There is a clear difference here, though. Making a change that could lead to poorly written libraries now being broken is clearly the fault of the change.
No, these libraries are already semantically broken in the same way e.g. libraries which didn't properly close their files and assumed the CPython refcounting GC would wipe there asses were broken.
They're already broken under two non-GIL'd implementations.
No, these libraries are already semantically broken in the same way e.g. libraries which didn't properly close their files and assumed the CPython refcounting GC would wipe there asses were broken.
They're already broken under two non-GIL'd implementations.