I feel like the talk at the language summit from the people behind Project Verona/Lungfish is very relevant to this discussion. They have a plan to add rust-like ownership semantics to Python, with the net effect of being able to turn races on any Python object into a runtime error, among other benefits. I’m not sure if there’s a public version of the slides that we saw at the language summit - but the general idea is summarized over in the discussion about their first step: adding a way to immortalize Python objects.
It’s a long-term plan, but also it appeals to me that we would also in the process fix incorrect multithreaded GIL-enabled workflows that trigger races on state tracked by the interpreter.
Maybe @stw can elaborate more on how his team’s work directly speaks to the concerns people are raising in this thread.