inspect.getclosurevars returns wrong globals dict

Open
#80,878 7 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
3/5
Estimated time
1-2 days
Newbie friendliness
35/100
Issue type
Bug
Clarity
Needs clarification
Activity status
Stale
Tech stack
python
Domain
devtools

Research direction

Start at Python's inspect.getclosurevars entry point in the library implementation and reproduce the reported wrong globals dict. Trace how the globals mapping is selected and compare it with the closure's expected globals; done means the function returns the correct mapping and the library behavior is covered by verification.

Written by the indexing model from the issue text.

Description

stdlib type-bug
BPO 36697
Nosy @ericvsmith, @1st1, @nitishch

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 = None
created_at = <Date 2019-04-22.08:49:29.424>
labels = ['type-bug', 'library']
title = 'inspect.getclosurevars returns wrong globals dict'
updated_at = <Date 2019-10-07.19:07:31.324>
user = 'https://bugs.python.org/llehtahw'

bugs.python.org fields:

activity = <Date 2019-10-07.19:07:31.324>
actor = 'Daniel Debrunner'
assignee = 'none'
closed = False
closed_date = None
closer = None
components = ['Library (Lib)']
creation = <Date 2019-04-22.08:49:29.424>
creator = 'llehtahw'
dependencies = []
files = []
hgrepos = []
issue_num = 36697
keywords = []
message_count = 6.0
messages = ['340645', '340707', '340708', '340710', '340753', '354128']
nosy_count = 5.0
nosy_names = ['eric.smith', 'yselivanov', 'nitishch', 'llehtahw', 'Daniel Debrunner']
pr_nums = []
priority = 'normal'
resolution = None
stage = None
status = 'open'
superseder = None
type = 'behavior'
url = 'https://bugs.python.org/issue36697'
versions = ['Python 3.6']

Dominant language
Python
Stars
77.2k
Forks
36k
Avg merge
1d 9h
Merged PRs (30d)
558

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from python/cpython

All issues in python/cpython

Similar issues

More Python issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.