Eric Promislow added the comment:
I found a workaround in our debugger code, so you can lower the priority on
this, or even mark it "Wontfix", although I still
think the frame stack is getting messed up.
One thing about our debugger, it essentially runs all the Python code in a big
exec statement, and this particular code contains its own exec stmt. The stack
looks wrong after we finish the inner exec statement.
So if you're looking for a repro, that might be the way to go. However
I can break at line 10 in the following code with no problem using pdb (Py 3):
1 #!/usr/bin/env python3
2
3 def inner_f(a, b):
4 ns2 = {"c": 7, "a":a, "b":b, "tot":None }
5 exec("tot = a + b + 1 + 100 * c", ns2)
6 return ns2['tot']
7
8 ns1 = {"c": 5, "inner_f": inner_f, "res":None }
9 exec("res = inner_f(3, 4) + 10 * c", ns1)
10 print("After all that, res: %d" % (ns1['res'],))
11 print("Stop here")
----------
_______________________________________
Python tracker <rep...@bugs.python.org>
<http://bugs.python.org/issue17971>
_______________________________________
_______________________________________________
Python-bugs-list mailing list
Unsubscribe:
http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
