Hello,
On Mon, 22 Feb 2021 17:32:23 -0500
Ned Batchelder <n...@nedbatchelder.com> wrote:
> On 2/22/21 3:06 PM, Paul Sokolovsky wrote:
> >
> > No, I'm proposing to stop faking lack of the last stack frame due to
> > CPython's implementation details. See the original message for more
> > info.
>
> I'm trying to understand what last stack frame (or lack of a last
> stack frame, or the faking of a lack of a last stack frame) you are
> talking about. Your original message shows some tracebacks, but
> doesn't have the code that produced them. It's hard to understand
> what you are referring to.
Well, if you looked at that stack trace, you saw the code:
Traceback (most recent call last):
File "pseudoc_tool.py", line 91, in <module>
first_class_function_value(func, **pass_params)
TypeError: print() got an unexpected keyword argument 'noann'
So yes, the code is:
---
first_class_function_value(func, **pass_params)
---
That's the "calling code". And the rest of the code? But's that's the
whole point, that the current CPython's error reporting doesn't tell me
where it is! It just tells me the function name, and go make a
full-text search thru the entire sys.path to find its location,
especially if there're many functions of that name.
--
Best regards,
Paul mailto:pmis...@gmail.com
_______________________________________________
Python-ideas mailing list -- python-ideas@python.org
To unsubscribe send an email to python-ideas-le...@python.org
https://mail.python.org/mailman3/lists/python-ideas.python.org/
Message archived at
https://mail.python.org/archives/list/python-ideas@python.org/message/6GFRPZSWTRZPJQKMWKBJVVPHD7X2ZMLO/
Code of Conduct: http://python.org/psf/codeofconduct/
