[issue26794] curframe can be None in pdb.py

Change by Irit Katriel : -- resolution: -> out of date stage: -> resolved status: open -> closed ___ Python tracker ___ ___

[issue26794] curframe can be None in pdb.py

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

[issue26794] curframe can be None in pdb.py

Jacek Pliszka added the comment: Haven't seen it since then. Stopped using 2.7 - using 3.6 in production and 3.7 in development now. I believe it can be closed. -- ___ Python tracker

[issue26794] curframe can be None in pdb.py

Irit Katriel added the comment: Maybe it was fixed in issue9230 -- ___ Python tracker ___ ___ Python-bugs-list mailing list

[issue26794] curframe can be None in pdb.py

Irit Katriel added the comment: Jacek, did you see this happen? My reading of the code is that curframe is initialized in setup(), which is called before curframe is accessed. It can later be modified in _select_frame. -- nosy: +iritkatriel ___

[issue26794] curframe can be None in pdb.py

Changes by SilentGhost : -- nosy: +georg.brandl ___ Python tracker ___ ___

[issue26794] curframe can be None in pdb.py

New submission from Jacek Pliszka: In /usr/lib64/python2.7/pdb.py in Pdb.default there is line: globals = self.curframe.f_globals curframe can be None so the line should be replaced by: globals = getattr(self.curframe, "f_globals", None) if hasattr(self, 'curframe') else None or something