[issue44417] bytecode<>line number mapping and f_lasti seem wrong in 3.10.0b2

[Gabriele N Tornetta]

Gabriele N Tornetta  added the comment:

I think I managed to find the source of the confusion. This seems to be due to 
https://github.com/python/cpython/commit/fcb55c0037baab6f98f91ee38ce84b6f874f034a,
 with the f_lasti from the C struct now being half of the value returned by the 
f_lasti attribute of the frame object (is this documented somewhere?).

--
stage:  -> resolved
status: open -> closed

___
Python tracker 

___
___
Python-bugs-list mailing list
Unsubscribe: 
https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com

[issue44417] bytecode<>line number mapping and f_lasti seem wrong in 3.10.0b2

[Mark Shannon]

Mark Shannon  added the comment:

What does "seem wrong" mean?
What exactly is the problem?

--

___
Python tracker 

___
___
Python-bugs-list mailing list
Unsubscribe: 
https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com

[issue44417] bytecode<>line number mapping and f_lasti seem wrong in 3.10.0b2

[Gabriele N Tornetta]

Change by Gabriele N Tornetta :


--
title: bytecode<>line number mapping seems wrong in 3.10.0b2 -> bytecode<>line 
number mapping and f_lasti seem wrong in 3.10.0b2

___
Python tracker 

___
___
Python-bugs-list mailing list
Unsubscribe: 
https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com