On Fri, Jan 1, 2016 at 10:36 AM, Mark Lawrence <breamore...@yahoo.co.uk> wrote: > On 31/12/2015 23:27, Ben Finney wrote: >> >> Chris Angelico <ros...@gmail.com> writes: >> >>> On Fri, Jan 1, 2016 at 7:18 AM, Ben Finney <ben+pyt...@benfinney.id.au> >>> wrote: >>>> >>>> Given how very often such decisions make my debugging tasks >>>> needlessly difficult, I'm not seeing how that's a desirable feature. >>> >>> >>> 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. >> > > Where did C code enter into this? What do the non C implementations do? > All I see is a dumb original suggestion that should be shot down in flames > as I see no merit in it at all.
I used the term "native code", because Jython and PyPy do the exact same thing that CPython does. (I haven't checked any others than those, but I wouldn't be surprised if they, too, had this distinction.) Short-handing to "C code" is close enough. ChrisA -- https://mail.python.org/mailman/listinfo/python-list