Changes by Alex <jalex.vig@gmail.com>: ---------- pull_requests: +2803 _______________________________________ Python tracker <report@bugs.python.org> <http://bugs.python.org/issue30951> _______________________________________

Change by Utkarsh Gupta <guptautkarsh2102@gmail.com>: ---------- keywords: +patch pull_requests: +9921 stage: -> patch review _______________________________________ Python tracker <report@bugs.python.org> <https://bugs.python.org/issue30951> _______________________________________

Serhiy Storchaka <storchaka+cpython@gmail.com> added the comment: co_names contains not only names of global variables. It contains also local names in the class scope, attribute names, names of imported modules, etc. ---------- nosy: +serhiy.storchaka _______________________________________ Python tracker <report@bugs.python.org> <https://bugs.python.org/issue30951> _______________________________________

Change by Cheryl Sabella <cheryl.sabella@gmail.com>: ---------- versions: +Python 3.8, Python 3.9 -Python 2.7, Python 3.3, Python 3.4, Python 3.5, Python 3.6, Python 3.7 _______________________________________ Python tracker <report@bugs.python.org> <https://bugs.python.org/issue30951> _______________________________________

Xavier Morel <xavier.morel@masklinn.net> added the comment: Maybe something along the lines of "names other than arguments and function locals", or "names of the symbols used in the code object, other than arguments and function locals"? This is still slightly confusing because in the case of an import the name is present in both mappings, but less so than the outright lie of the current version. Serhiy, is there a way to access the class's code object from Python? Also does that mean varnames is not used by class code objects despite it stating unambiguously that it stores locals? ---------- nosy: +xmorel _______________________________________ Python tracker <report@bugs.python.org> <https://bugs.python.org/issue30951> _______________________________________