bdb calls linecache.checkcache, resulting in source being different from code

Open
#84,148 1 comment 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

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

Research direction

Start by reading the bdb and linecache modules, then inspect the referenced PR python/cpython#19013 for the proposed fix and its context. Confirm the behavior that causes source to differ from code and use the PR's tests or reproduction to verify the issue is resolved.

Written by the indexing model from the issue text.

Description

3.9 (EOL) stdlib
BPO 39967
Nosy @blueyed
PRs
  • python/cpython#19013
    		•

    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 2020-03-15.09:27:24.930>
labels = ['library', '3.9']
title = 'bdb calls linecache.checkcache, resulting in source being different from code'
updated_at = <Date 2020-03-15.09:28:41.231>
user = 'https://github.com/blueyed'

    bugs.python.org fields:

    activity = <Date 2020-03-15.09:28:41.231>
actor = 'blueyed'
assignee = 'none'
closed = False
closed_date = None
closer = None
components = ['Library (Lib)']
creation = <Date 2020-03-15.09:27:24.930>
creator = 'blueyed'
dependencies = []
files = []
hgrepos = []
issue_num = 39967
keywords = ['patch']
message_count = 1.0
messages = ['364224']
nosy_count = 1.0
nosy_names = ['blueyed']
pr_nums = ['19013']
priority = 'normal'
resolution = None
stage = 'patch review'
status = 'open'
superseder = None
type = None
url = 'https://bugs.python.org/issue39967'
versions = ['Python 3.9']

    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.