The interpreter's local variables panel doesn't take account of renamed variables. In addition, it needs to take into account the current interpreter source code view to determine which set of variables to show.
For example, in the JS view variable numbering is used to avoid scope conflicts. However, they are lost at the end of the block scope, instead of the function scope. In the ML view, the same renumbered variable shows when it is not even present in the displayed source. In this mode, the renumbered variables should be collapsed into the original variable name.
One particularly confusing case at the moment is complete_property_descriptor.
The interpreter's local variables panel doesn't take account of renamed variables. In addition, it needs to take into account the current interpreter source code view to determine which set of variables to show.
For example, in the JS view variable numbering is used to avoid scope conflicts. However, they are lost at the end of the block scope, instead of the function scope. In the ML view, the same renumbered variable shows when it is not even present in the displayed source. In this mode, the renumbered variables should be collapsed into the original variable name.
One particularly confusing case at the moment is
complete_property_descriptor.