Skip to content
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 our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Make pdb.orig_set_trace available #142

Closed
wants to merge 1 commit into from
Closed

Make pdb.orig_set_trace available #142

wants to merge 1 commit into from

Conversation

blueyed
Copy link
Collaborator

@blueyed blueyed commented Mar 7, 2019

Seems to be necessary for PYTHONBREAKPOINT.

PYTHONBREAKPOINT=pdb.pdb.set_trace python -c 'breakpoint()'
-c:1: RuntimeWarning: Ignoring unimportable $PYTHONBREAKPOINT: "pdb.pdb.set_trace"

I have improved this for pytest's --pdbcls to also handle attributes, but am not sure if it is acceptable/worth it for Python itself..
Ref: pytest-dev/pytest#4855

@blueyed blueyed changed the title Make pdb.orig_set_trace available [RFC] Make pdb.orig_set_trace available Mar 7, 2019
@blueyed blueyed requested a review from antocuni March 9, 2019 15:27
@blueyed blueyed changed the title [RFC] Make pdb.orig_set_trace available Make pdb.orig_set_trace available Apr 24, 2019
@blueyed blueyed closed this May 25, 2019
@blueyed blueyed deleted the orig_set_trace branch May 25, 2019 14:42
@blueyed blueyed restored the orig_set_trace branch May 28, 2019 14:43
@blueyed blueyed reopened this May 28, 2019
@blueyed blueyed closed this May 28, 2019
@blueyed blueyed reopened this May 28, 2019
@blueyed
Copy link
Collaborator Author

blueyed commented Oct 22, 2019

PDBPP_HIJACK_PDB=0 can be used (I guess)

@blueyed blueyed closed this Oct 22, 2019
@blueyed blueyed deleted the orig_set_trace branch October 22, 2019 05:17
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

2 participants