Movatterモバイル変換


[0]ホーム

URL:


Skip to content

Navigation Menu

Sign in
Appearance settings

Search code, repositories, users, issues, pull requests...

Provide feedback

We read every piece of feedback, and take your input very seriously.

Saved searches

Use saved searches to filter your results more quickly

Sign up
Appearance settings

gh-120254: Add acommands argument topdb.set_trace#120255

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.

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

Already on GitHub?Sign in to your account

Merged
gaogaotiantian merged 10 commits intopython:mainfromgaogaotiantian:pdb-commands
Sep 24, 2024

Conversation

@gaogaotiantian
Copy link
Member

@gaogaotiantiangaogaotiantian commentedJun 8, 2024
edited by github-actionsbot
Loading

Comment on lines 214 to 215
The *commands* argument, if given, would be a list of commands to execute
when the debugger starts. It has similar effects to the:file:`.pdbrc` file.
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others.Learn more.

Suggested change
The *commands* argument, if given, would be a list of commands to execute
when the debugger starts. It has similar effects to the:file:`.pdbrc` file.
The *commands* argument, if given, is a list of commands to execute
when the debugger starts. Those commands are executed after those
optionally provided by the:file:`.pdbrc` file.

Copy link
MemberAuthor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others.Learn more.

Do you think two "those" is a little bit confusing here? How about These commands are executed after any commands optionally provided by the :file:.pdbrc file?

Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others.Learn more.

I agree the double "those" is confusing.

Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others.Learn more.

Oups, you're right! I'm sorry I didn't reply to your question 3 weeks ago btw, but yes your suggestion is way better!

@@ -0,0 +1 @@
Added ``commands`` argument to:class:`pdb.Pdb` which allows user to send debugger commands in the source file.
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others.Learn more.

Suggested change
Added ``commands`` argument to:class:`pdb.Pdb` which allowsuser to send debugger commands in the source file.
Added ``commands`` argument to:class:`pdb.Pdb` which allowsusers to send debugger commands in the source file.

.pdbrc files from the filesystem.

The *commands* argument, if given, would be a list of commands to execute
when the debugger starts. It has similar effects to the:file:`.pdbrc` file.
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others.Learn more.

The phrase “similar effects” is kind of vague. I am not sure how to say it more precisely. Link to the.pdbrc documentation? Not sure.

@gaogaotiantian
Copy link
MemberAuthor

I moved this argument toset_trace() where it makes more sense. Partially due to the impact of#121451 - we won't create aPdb instance every time we try to bring up a debugger.

@gaogaotiantian
Copy link
MemberAuthor

Hi@brandtbucher , could you take a look at this feature and see if it's reasonable to add?

brandtbucher reacted with thumbs up emoji

Copy link
Member

@brandtbucherbrandtbucher left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others.Learn more.

Thanks a lot for your patience.

Finally got a chance to play with it... I loved finding out thatbreakpoint(commands=[...]) works now! I think this is a great change.

@gaogaotiantian
Copy link
MemberAuthor

@brandtbucher do you think this needs a whatsnew entry?

@brandtbucher
Copy link
Member

I think NEWS is probably good enough, but you can certainly add it to What's New if you feel it's something that you want to publicize more! Adding and removing stuff from that doc is pretty lightweight.

@gaogaotiantiangaogaotiantian changed the titlegh-120254: Add acommands argument topdb.Pdbgh-120254: Add acommands argument topdb.set_traceSep 24, 2024
@gaogaotiantian
Copy link
MemberAuthor

I'll just merge this then!

@gaogaotiantiangaogaotiantian merged commitaf8403a intopython:mainSep 24, 2024
2 checks passed
@gaogaotiantiangaogaotiantian deleted the pdb-commands branchSeptember 24, 2024 19:52
Sign up for freeto join this conversation on GitHub. Already have an account?Sign in to comment

Reviewers

@picnixzpicnixzpicnixz left review comments

@brandtbucherbrandtbucherbrandtbucher approved these changes

+2 more reviewers

@mceplmceplmcepl left review comments

@DelengowskiDelengowskiDelengowski left review comments

Reviewers whose approvals may not affect merge requirements

Assignees

No one assigned

Labels

None yet

Projects

None yet

Milestone

No milestone

Development

Successfully merging this pull request may close these issues.

5 participants

@gaogaotiantian@brandtbucher@mcepl@picnixz@Delengowski

[8]ページ先頭

©2009-2025 Movatter.jp