Pdb.set_trace debugging does not end correctly

未关闭
#66,196 6 条评论 0 个 reaction 已指派 0 人 在 GitHub 查看

还没有人认领这个 Issue。

评估

难度
4/5
预计耗时
3-5 天
新手友好度
10/100
Issue 类型
缺陷
描述清晰度
需要澄清
活跃度
停滞
技术栈
python
领域
devtools

调研方向

Start by reading the migrated bpo-21997 details and the superseding bpo-16446 entry, then investigate the Pdb.set_trace behavior described in the title. Confirm whether the superseding issue covers this report; done means debugging exits correctly without the reported lingering behavior.

由索引模型根据 Issue 内容生成。

描述

stdlib type-bug
BPO 21997
Nosy @birkenfeld, @terryjreedy, @bitdancer, @xdegaye, @pppery
Superseder
  • bpo-16446: pdb raises BdbQuit on 'quit' when started with set_trace
    		•

    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 2014-07-17.15:52:11.617>
labels = ['type-bug', 'library']
title = 'Pdb.set_trace debugging does not end correctly'
updated_at = <Date 2016-08-24.13:35:22.081>
user = 'https://github.com/pppery'

    bugs.python.org fields:

    activity = <Date 2016-08-24.13:35:22.081>
actor = 'r.david.murray'
assignee = 'none'
closed = False
closed_date = None
closer = None
components = ['Library (Lib)']
creation = <Date 2014-07-17.15:52:11.617>
creator = 'ppperry'
dependencies = []
files = []
hgrepos = []
issue_num = 21997
keywords = []
message_count = 6.0
messages = ['223342', '223463', '223482', '223506', '273557', '273558']
nosy_count = 5.0
nosy_names = ['georg.brandl', 'terry.reedy', 'r.david.murray', 'xdegaye', 'ppperry']
pr_nums = []
priority = 'normal'
resolution = None
stage = 'resolved'
status = 'open'
superseder = '16446'
type = 'behavior'
url = 'https://bugs.python.org/issue21997'
versions = ['Python 2.7', 'Python 3.4', 'Python 3.5']

    主要语言
    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 摘要。