tokenize the source to manage Pdb breakpoints

未關閉
#59,118 4 則留言 0 個 reaction 已指派 0 人 在 GitHub 檢視

還沒有人認領這個 Issue。

評估

難度
4/5
預估耗時
3-5 天
新手友好度
25/100
Issue 類型
缺陷
描述清晰度
需要釐清
活躍度
停滯
技術堆疊
python
領域
devtools

研究方向

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.

由索引模型根據 Issue 內容生成。

描述

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']
    

    主要語言
    Python
    星號
    77.2k
    分支
    36k
    平均合併
    1 天 9 小時
    30 天內合併 PR
    558

    貢獻指南

    開啟貢獻指南

    從這裡開始

    1. 先讀完整個 Issue,再讀專案的貢獻指南。
    2. 在 Issue 下留言說明你要接手 —— 這能避免兩個人做同樣的事。
    3. Fork 儲存庫,在一個分支上完成修改。
    4. 送出 Pull Request,並在描述裡引用這個 Issue 編號。

    python/cpython 的其他 Issue

    查看 python/cpython 的全部 Issue

    相似的 Issue

    更多 Python Issue

    把新 issue 寄到你的電子郵件信箱

    精選適合新手參與的 GitHub issue 摘要。