inspect.getframeinfo() doesn't handle frames without lineno
Open
Nobody has claimed this yet.
interpreter-core
stdlib
triaged
type-bug
- Dominant language
- Python
- Stars
- 77.2k
- Forks
- 36k
- PR merge metrics
- PR metrics pending
Description
| BPO | 45563 |
|---|---|
| Nosy | @malemburg, @markshannon, @graingert, @lysnikolaou, @pablogsal |
| PRs |
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 2021-10-21.22:02:12.400>
labels = ['interpreter-core', 'library', '3.10']
title = "inspect.getframeinfo() doesn't handle frames without lineno"
updated_at = <Date 2022-03-22.10:52:45.856>
user = 'https://github.com/malemburg'
bugs.python.org fields:
activity = <Date 2022-03-22.10:52:45.856>
actor = 'Mark.Shannon'
assignee = 'none'
closed = False
closed_date = None
closer = None
components = ['Interpreter Core', 'Library (Lib)']
creation = <Date 2021-10-21.22:02:12.400>
creator = 'lemburg'
dependencies = []
files = []
hgrepos = []
issue_num = 45563
keywords = ['patch']
message_count = 11.0
messages = ['404674', '404745', '404763', '404765', '404800', '404802', '404808', '404830', '404835', '404861', '415758']
nosy_count = 5.0
nosy_names = ['lemburg', 'Mark.Shannon', 'graingert', 'lys.nikolaou', 'pablogsal']
pr_nums = ['32044']
priority = 'normal'
resolution = None
stage = 'patch review'
status = 'open'
superseder = None
type = None
url = 'https://bugs.python.org/issue45563'
versions = ['Python 3.10']
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start at the inspect.getframeinfo() entry point and investigate how it behaves for frames without a lineno. The issue references Python 3.10 and PR #32044; done means the reported case is handled, with the expected behavior confirmed by relevant tests.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- python
- Domain
- backend
- Issue type
- Bug
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100