[issue22577] local variable changes lost after pdb jump command

Change by Irit Katriel : -- resolution: -> fixed stage: patch review -> resolved status: open -> closed ___ Python tracker ___ ___

[issue22577] local variable changes lost after pdb jump command

Change by Georg Brandl : -- nosy: -georg.brandl ___ Python tracker ___ ___ Python-bugs-list mailing list Unsubscribe:

[issue22577] local variable changes lost after pdb jump command

Irit Katriel added the comment: This is now resolved, on Python 3.10 I get: >python -m pdb tmp1.py Running Release|Win32 interpreter... > c:\users\user\src\cpython\tmp1.py(1)() -> def foo(x): (Pdb) jump 4 > c:\users\user\src\cpython\tmp1.py(4)() -> lineno = 4 (Pdb) q

[issue22577] local variable changes lost after pdb jump command

Henry Chen added the comment: PEP 558 will fix this issue, which I've verified with the proposed implementation (https://github.com/python/cpython/pull/3640/files). Perhaps this issue can be closed? -- ___ Python tracker

[issue22577] local variable changes lost after pdb jump command

Change by Henry Chen : -- nosy: +henry ___ Python tracker ___ ___ Python-bugs-list mailing list Unsubscribe:

[issue22577] local variable changes lost after pdb jump command

Change by Roundup Robot : -- keywords: +patch pull_requests: +10278 stage: -> patch review ___ Python tracker ___ ___

[issue22577] local variable changes lost after pdb jump command

New submission from Xavier de Gaye: With the following pdb_jump.py script: def foo(x): import pdb; pdb.set_trace() lineno = 3 lineno = 4 foo(1) The change made to 'x' is lost after a jump to line 4: $ ./python ~/tmp/test/pdb_jump.py ~/tmp/test/pdb_jump.py(3)foo() - lineno = 3