Thomas Haller added the comment:
> We could keep f_lineno unchanged, despite the fact that its value can be wrong
It was not completely wrong. It was seemingly good enough for the past 20+
years.
The change in behaviour is one thing. It's also inconvenient that, even when
being
Thomas Haller added the comment:
OK, I see. Thanks for the references.
FWIW, I think such changes in behavior are really bad. The issue should be
fixed without changing existing API.
--
___
Python tracker
<https://bugs.python.org/issue38
Thomas Haller added the comment:
Do you have a reference to the discussion about that?
--
___
Python tracker
<https://bugs.python.org/issue38283>
___
___
Pytho
Change by Thomas Haller :
--
components: +Interpreter Core
type: -> behavior
versions: +Python 3.8
___
Python tracker
<https://bugs.python.org/issu
New submission from Thomas Haller :
The line number for the frame object changed behaviour in 3.8.
I am seeing this on Fedora rawhide, which ships "3.8.0~b4-1.fc32" package.
That happens when wrapping lines for calling functions.
Before, the line number sys._getframe(1).f_lineno in
