8000 Improve the `filename` argument of `pdb`'s `break` command · Issue #117618 · python/cpython · GitHub
[go: up one dir, main page]
Skip to content

Improve the filename argument of pdb's break command #117618

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom
Closed
gaogaotiantian opened this issue Apr 8, 2024 · 0 comments
Closed

Improve the filename argument of pdb's break command #117618

gaogaotiantian opened this issue Apr 8, 2024 · 0 comments
Labels
type-feature A feature request or enhancement

Comments

@gaogaotiantian
Copy link
Member
gaogaotiantian commented Apr 8, 2024 •
edited by bedevere-app bot
Loading

Feature or enhancement

Proposal:

Currently in the docs we say b(reak) command can take a filename, but we are very vague about it. It only mentioned the file will be searched in sys.path.

The actual implementation currently allows:

  • absolute path
  • relative path (including a path with /, so not only "filename")
  • module name (only if module.py is in sys.path)

As you can tell, we allow module name like pprint:100, but not package.module like multiprocessing.queue:100, however, multiprocessing/queue.py:100 works. This is inconsistent by itself, let alone the lack of description.

I'm making a PR to clean this up a bit. This PR will improve the lookupmodule function to support package.module, and clean up both code and docs.

Has this already been discussed elsewhere?

This is a minor feature, which does not need previous discussion elsewhere

Links to previous discussion of this feature:

No response

Linked PRs
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
type-feature A feature request or enhancement
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
1 participant
@gaogaotiantian
0