[issue9633] pdb go stack up/down

2020-10-22 Thread Irit Katriel
Irit Katriel added the comment: I've reproduced the bug on 3.10. -- nosy: +iritkatriel versions: +Python 3.10, Python 3.8, Python 3.9 -Python 3.2 ___ Python tracker ___

[issue9633] pdb go stack up/down

2019-04-23 Thread daniel hahler
Change by daniel hahler : -- nosy: +blueyed ___ Python tracker ___ ___ Python-bugs-list mailing list Unsubscribe:

[issue9633] pdb go stack up/down

2018-12-10 Thread Henry Chen
Change by Henry Chen : -- pull_requests: +10309 stage: -> patch review ___ Python tracker ___ ___ Python-bugs-list mailing list

[issue9633] pdb go stack up/down

2017-10-14 Thread Nick Coghlan
Nick Coghlan added the comment: Note that we're currently looking into this as something that could be potentially addressed by PEP 558 and any related changes to the way that function locals interact with trace hooks: https://bugs.python.org/issue30744#msg304388

[issue9633] pdb go stack up/down

2017-10-14 Thread Nick Coghlan
Change by Nick Coghlan : -- nosy: +ncoghlan ___ Python tracker ___ ___ Python-bugs-list

[issue9633] pdb go stack up/down

2013-03-28 Thread Georg Brandl
Changes by Georg Brandl ge...@python.org: -- assignee: georg.brandl - ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue9633 ___ ___ Python-bugs-list

[issue9633] pdb go stack up/down

2012-12-05 Thread Andrew Svetlov
Changes by Andrew Svetlov andrew.svet...@gmail.com: -- nosy: +asvetlov ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue9633 ___ ___ Python-bugs-list

[issue9633] pdb go stack up/down

2012-11-24 Thread Xavier de Gaye
Xavier de Gaye added the comment: It is not only the up and down commands; the where, longlist and source commands may also overwrite changes made to f_locals. In Markus sample script above, and with the patch applied, when the change made to stack_2 is followed by a step command, stack_2 value

[issue9633] pdb go stack up/down

2010-09-01 Thread Meador Inge
Meador Inge mead...@gmail.com added the comment: I believe this is slightly tricky because 'bdb.format_stack_entry' makes references to '.f_locals' and 'bdb.format_stack_entry' is invoked in several places in 'pdb'. One option would be to add a extra parameter to 'bdb.format_stack_entry' to

[issue9633] pdb go stack up/down

2010-08-30 Thread Meador Inge
Changes by Meador Inge mead...@gmail.com: -- nosy: +meador.inge ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue9633 ___ ___ Python-bugs-list

[issue9633] pdb go stack up/down

2010-08-18 Thread Markus Pröller
New submission from Markus Pröller mproel...@googlemail.com: Hello, with python 2.7 I encounter the following problem: I have created the following sample script: import pdb def function_1(number): stack_1 = number function_2(stack_1) def function_2(number): stack_2 = number

[issue9633] pdb go stack up/down

2010-08-18 Thread Éric Araujo
Éric Araujo mer...@netwok.org added the comment: Thank you for the report. I don’t know pdb much, but I assume you have checked the doc to make sure this is indeed a bug. Can you test it with 3.1 and 3.2 too? Bug tracker tip: You can find if a core developer is interested in a module in

[issue9633] pdb go stack up/down

2010-08-18 Thread Georg Brandl
Georg Brandl ge...@python.org added the comment: The problem here is that changes in the locals are only saved back to the frame when leaving the trace function, and up/down don't do that. This could be fixed by making Pdb.curframe_locals a dictionary for all visited frames while interaction