traceback & inspect modules should verify that the .py source file matches the one that the running process is using
Open
Nobody has claimed this yet.
3.11
stdlib
type-feature
- Dominant language
- Python
- Stars
- 77.2k
- Forks
- 36k
- PR merge metrics
- PR metrics pending
Description
| BPO | 44091 |
|---|---|
| Nosy | @gvanrossum, @gpshead, @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 = None
created_at = <Date 2021-05-09.17:15:30.610>
labels = ['type-feature', 'library', '3.11']
title = 'traceback & inspect modules should verify that the .py source file matches the one that the running process is using'
updated_at = <Date 2021-09-02.20:42:48.048>
user = 'https://github.com/gpshead'
bugs.python.org fields:
activity = <Date 2021-09-02.20:42:48.048>
actor = 'gregory.p.smith'
assignee = 'none'
closed = False
closed_date = None
closer = None
components = ['Library (Lib)']
creation = <Date 2021-05-09.17:15:30.610>
creator = 'gregory.p.smith'
dependencies = []
files = []
hgrepos = []
issue_num = 44091
keywords = []
message_count = 6.0
messages = ['393328', '400866', '400867', '400869', '400870', '400956']
nosy_count = 3.0
nosy_names = ['gvanrossum', 'gregory.p.smith', 'iritkatriel']
pr_nums = []
priority = 'normal'
resolution = None
stage = 'needs patch'
status = 'open'
superseder = None
type = 'enhancement'
url = 'https://bugs.python.org/issue44091'
versions = ['Python 3.11']
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 by locating the traceback and inspect module implementations and their existing tests. Reproduce a case where the running process uses a different .py source file from the one on disk, then establish tests covering the verification behavior. Done means both modules reliably detect or handle that mismatch.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- python
- Domain
- tooling
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100