pdb: Add step / next count arguments
Open
Nobody has claimed this yet.
3.7 (EOL)
stdlib
type-feature
- Dominant language
- Python
- Stars
- 77.2k
- Forks
- 36k
- PR merge metrics
- PR metrics pending
Description
| BPO | 30761 |
|---|---|
| Nosy | @warsaw, @rhettinger, @vstinner, @xdegaye, @mlouielu |
| PRs |
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 2017-06-26.10:10:13.014>
labels = ['3.7', 'type-feature', 'library']
title = 'pdb: Add step / next count arguments'
updated_at = <Date 2017-08-26.19:29:59.821>
user = 'https://github.com/mlouielu'
bugs.python.org fields:
activity = <Date 2017-08-26.19:29:59.821>
actor = 'barry'
assignee = 'none'
closed = False
closed_date = None
closer = None
components = ['Library (Lib)']
creation = <Date 2017-06-26.10:10:13.014>
creator = 'louielu'
dependencies = []
files = []
hgrepos = []
issue_num = 30761
keywords = []
message_count = 4.0
messages = ['296869', '296871', '296906', '296930']
nosy_count = 5.0
nosy_names = ['barry', 'rhettinger', 'vstinner', 'xdegaye', 'louielu']
pr_nums = ['2399']
priority = 'normal'
resolution = None
stage = None
status = 'open'
superseder = None
type = 'enhancement'
url = 'https://bugs.python.org/issue30761'
versions = ['Python 3.7']
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
The issue concerns the pdb debugger and asks for count arguments for the step and next commands. Start by reviewing the existing pdb command entry points and the referenced pull request python/cpython#2399; done means the commands accept and correctly handle the requested counts with appropriate tests.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- python
- Domain
- devtools
- Issue type
- Feature
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 25/100