tokenize the source to manage Pdb breakpoints

Open
#59,118 4 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

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

Research direction

Start by reviewing the attached pdb_default.patch, pdb_default_2.patch, and pdb_lnotab.patch files alongside the original BPO issue. Trace the existing Pdb breakpoint handling and tests, then establish how source tokenization should change breakpoint management and how the resulting behavior will be verified.

Written by the indexing model from the issue text.

Description

stdlib type-bug
BPO 14913
Nosy @birkenfeld, @asvetlov, @xdegaye
Files
  • pdb_default.patch
  • pdb_default_2.patch
  • pdb_lnotab.patch
    		•

    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 2012-05-25.11:49:13.311>
labels = ['type-bug', 'library']
title = 'tokenize the source to manage Pdb breakpoints'
updated_at = <Date 2012-12-05.11:07:36.486>
user = 'https://github.com/xdegaye'

    bugs.python.org fields:

    activity = <Date 2012-12-05.11:07:36.486>
actor = 'asvetlov'
assignee = 'none'
closed = False
closed_date = None
closer = None
components = ['Library (Lib)']
creation = <Date 2012-05-25.11:49:13.311>
creator = 'xdegaye'
dependencies = []
files = ['25704', '26050', '27565']
hgrepos = []
issue_num = 14913
keywords = ['patch']
message_count = 4.0
messages = ['161570', '163182', '172877', '176279']
nosy_count = 3.0
nosy_names = ['georg.brandl', 'asvetlov', 'xdegaye']
pr_nums = []
priority = 'normal'
resolution = None
stage = None
status = 'open'
superseder = None
type = 'behavior'
url = 'https://bugs.python.org/issue14913'
versions = ['Python 3.4']

    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.