[issue44749] LOAD_NAME not using PyObject_GetItem when globals() is a dict subclass

Douglas Raillard added the comment: I ended up with a slightly different API that allows me to preemptively set some global names before the code runs in the module, so my use case sort of vanished. I don't think there is a real need of beating the dead horse here. My only suggestion on the

[issue44749] LOAD_NAME not using PyObject_GetItem when globals() is a dict subclass

Terry J. Reedy added the comment: If you want to change that decision, I suggest posting on python-ideas list explaining why you disagree and get support for a change now. -- ___ Python tracker

[issue44749] LOAD_NAME not using PyObject_GetItem when globals() is a dict subclass

Terry J. Reedy added the comment: Both preceding issues were closed as rejected. -- nosy: +terry.reedy resolution: -> duplicate stage: -> resolved status: open -> closed superseder: -> Inconsistent behavior if globals is a dict subclass type: -> enhancement versions: -Python 3.10

[issue44749] LOAD_NAME not using PyObject_GetItem when globals() is a dict subclass

Douglas Raillard added the comment: Looks like it is, for some reason I did not find these previous issues when looking for existing ones. -- ___ Python tracker ___ _

[issue44749] LOAD_NAME not using PyObject_GetItem when globals() is a dict subclass

Inada Naoki added the comment: Is this issue duplicate of https://bugs.python.org/issue32615 and https://bugs.python.org/issue1402289 ? -- nosy: +methane ___ Python tracker _

[issue44749] LOAD_NAME not using PyObject_GetItem when globals() is a dict subclass

New submission from Douglas Raillard : Re-raising the bug reported by Kevin Shweh: thread: https://bugs.python.org/issue14385 message: https://bugs.python.org/msg337245 Here is a copy for easier reference: The patch for this issue changed LOAD_GLOBAL to use PyObject_GetItem when globals() is