A point on the safety/correctness front: I remembered we already run arbitrary code at roughly this point in the eval loop, as we have to invoke __iter__ to get the exceptions to check when an iterable is used in except clause.

That means allowing the subclass check hooks to run here isn't as radical a change as I first thought.