Pdb.set_trace debugging does not end correctly

Open
#66,196 6 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

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

Research direction

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.

Written by the indexing model from the issue text.

Description

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

    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.