Pdb breakpoints don't work on lines without bytecode

Open
#50,571 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
25/100
Issue type
Bug
Clarity
Needs clarification
Activity status
Stale
Tech stack
python
Domain
devtools

Research direction

Start by reviewing linked PR gh-145121 and the migrated issue details for the debugger behavior around lines without bytecode. Completion means Pdb breakpoints can be set and hit on those lines; the payload names no source file or test, so locate the relevant debugger tests before proceeding.

Written by the indexing model from the issue text.

Description

stdlib type-bug
BPO 6322
Nosy @birkenfeld, @asvetlov, @xdegaye

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 2009-06-22.14:09:13.334>
labels = ['type-bug', 'library']
title = "Pdb breakpoints don't work on lines without bytecode"
updated_at = <Date 2012-11-24.11:01:15.525>
user = 'https://bugs.python.org/inducer'

bugs.python.org fields:

activity = <Date 2012-11-24.11:01:15.525>
actor = 'xdegaye'
assignee = 'none'
closed = False
closed_date = None
closer = None
components = ['Library (Lib)']
creation = <Date 2009-06-22.14:09:13.334>
creator = 'inducer'
dependencies = []
files = []
hgrepos = []
issue_num = 6322
keywords = []
message_count = 5.0
messages = ['89597', '109903', '171826', '172878', '176278']
nosy_count = 4.0
nosy_names = ['georg.brandl', 'inducer', 'asvetlov', 'xdegaye']
pr_nums = []
priority = 'normal'
resolution = None
stage = 'needs patch'
status = 'open'
superseder = None
type = 'behavior'
url = 'https://bugs.python.org/issue6322'
versions = ['Python 3.1', 'Python 2.7', 'Python 3.2']

Linked PRs
  • gh-145121
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.