You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
These offsets are no longer used for anything in the overwhelming
majority of cases. The only way that they could be used is if a process
running a modern version of Python managed to trash memory in a way that
corrupted the `_Py_DebugOffsets` structure in memory. And unfortunately,
even in that case, we would go on to behave incorrectly: the Python 3.14
debug offsets were wrong.
Since these aren't being used and haven't been being well maintained,
and since they're impossible to properly test, and since they're
impossible to make work for multiple different interpreter flavors (GIL
vs free-threading, JIT vs no-JIT, etc) and they could even change
between two patch versions of the interpreter for the same flavor, let's
just remove them and turn it into a hard failure if someone manages to
trash memory so badly that the `_Py_DebugOffsets` structure can't be
used.
Signed-off-by: Matt Wozniski <mwozniski@bloomberg.net>
0 commit comments