> IMO type checking is to python what bounds checking is to C. Interesting analogy, but in my experience it doesn't hold up. If you have a Python typing bug,

> IMO type checking is to python what bounds checking is to C. Interesting analogy, but in my experience it doesn't hold up. If you have a Python typing bug, it will crash your program almost immediately and you can quickly catch it and fix it. In contrast, C boundary checking issues often come up in relatively rare corner cases, and when they do occur, they often do not result in an exception / error especially if the memory is already paged and set to zero. In production code, boundary checking errors in C occur all the time, but Python type bugs are pretty rare.