raise None

Thu Dec 31 18:36:18 EST 2015

On 31/12/2015 23:27, Ben Finney wrote:
> Chris Angelico <rosuav at gmail.com> writes:
>>> On Fri, Jan 1, 2016 at 7:18 AM, Ben Finney <ben+python at 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.
-- 
My fellow Pythonistas, ask not what our language can do for you, ask
what you can do for our language.
Mark Lawrence