[issue13328] pdb shows code from wrong module

2020-01-24 Thread Brett Cannon
Change by Brett Cannon : -- nosy: -brett.cannon ___ Python tracker ___ ___ Python-bugs-list mailing list Unsubscribe: https://mail

[issue13328] pdb shows code from wrong module

2012-12-05 Thread Xavier de Gaye
Changes by Xavier de Gaye : -- nosy: +xdegaye ___ Python tracker ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.pytho

[issue13328] pdb shows code from wrong module

2011-11-05 Thread Meador Inge
Changes by Meador Inge : -- nosy: +meador.inge ___ Python tracker ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.pyth

[issue13328] pdb shows code from wrong module

2011-11-03 Thread Petri Lehtinen
Changes by Petri Lehtinen : -- nosy: +petri.lehtinen ___ Python tracker ___ ___ Python-bugs-list mailing list Unsubscribe: http://mai

[issue13328] pdb shows code from wrong module

2011-11-02 Thread Antoine Pitrou
Changes by Antoine Pitrou : -- nosy: +brett.cannon, georg.brandl, ncoghlan ___ Python tracker ___ ___ Python-bugs-list mailing list Un

[issue13328] pdb shows code from wrong module

2011-11-02 Thread Arkadiusz Wahlig
Arkadiusz Wahlig added the comment: How to reproduce: Given a module foo.py imported using zipimport with a function bar, if we try to set a breakpoint in bar using: > break foo.bar pdb would take filename and lineno from the function object but would use current frame to get module globals

[issue13328] pdb shows code from wrong module

2011-11-02 Thread Arkadiusz Wahlig
New submission from Arkadiusz Wahlig : If pdb is used to debug code using zipimport, it may end up displaying source code from wrong module. Python will execute the correct code but the source code lines displayed by pdb (including the "list" command) will come from an unrelated module. Reaso