curframe can be None in pdb.py

[JacekPliszka]

BPO	26794
Nosy	@iritkatriel

^{Note: these values reflect the state of the issue at the time it was migrated and might not reflect the current state.}

Show more details

GitHub fields:

assignee = None
closed_at = <Date 2020-10-19.22:29:44.302>
created_at = <Date 2016-04-18.07:47:44.215>
labels = ['library', 'type-crash']
title = 'curframe can be None in pdb.py'
updated_at = <Date 2020-10-19.22:29:44.301>
user = 'https://bugs.python.org/JacekPliszka'

bugs.python.org fields:

activity = <Date 2020-10-19.22:29:44.301>
actor = 'iritkatriel'
assignee = 'none'
closed = True
closed_date = <Date 2020-10-19.22:29:44.302>
closer = 'iritkatriel'
components = ['Library (Lib)']
creation = <Date 2016-04-18.07:47:44.215>
creator = 'Jacek.Pliszka'
dependencies = []
files = []
hgrepos = []
issue_num = 26794
keywords = []
message_count = 4.0
messages = ['263652', '375777', '375778', '375797']
nosy_count = 2.0
nosy_names = ['Jacek.Pliszka', 'iritkatriel']
pr_nums = []
priority = 'normal'
resolution = 'out of date'
stage = 'resolved'
status = 'closed'
superseder = None
type = 'crash'
url = 'https://bugs.python.org/issue26794'
versions = ['Python 2.7']

[JacekPliszka]

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 should be done in different way in setup

[iritkatriel]

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.

[iritkatriel]

Maybe it was fixed in bpo-9230

[JacekPliszka]

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.