Ben Finney <[email protected]>: > Chris Angelico <[email protected]> writes: >> What Steven's actually advocating is removing a difference between >> Python code and native code. > > Sure, but his proposal is to move in the direction of *less* debugging > information. > > If I could have the traceback continue into the C code and tell me the > line of C code that raised the exception, *that's* what I'd choose. > > The debugging information barrier of the C–Python boundary is a > practical limitation, not a desirable one. I think those barriers > should be as few as possible, and don't agree with enabling more of > them.
I think I agree with you. Don't check anything; let it crash and burn if the input spec is violated. Marko -- https://mail.python.org/mailman/listinfo/python-list
