> The hardest part of debugging Python is "hitting the wall" when you come to a native library (compiled C code). This is one big reason I love Pharo and other

> The hardest part of debugging Python is "hitting the wall" when you come to a native library (compiled C code). This is one big reason I love Pharo and other Smalltalk-language implementations. Being mostly written in themselves down to the VM. You can take a deep dive and inspect everything without being afraid of smashing your head against C bedrock underneath. And they still manage doing this while being reasonably performant and dynamic.