[Python-Dev] PEP 553
yarkot1 at gmail.com
Wed Oct 4 20:22:56 EDT 2017
Barry suggested I bring this up here.
It seems the right time to at least discuss this:
RE: PEP 553 enabling / disabling breakpoints ---
I've recently started using a simple conditional breakpoint in ipython, and
wonder if - in addition to Nick Coghlan's request for the env
'PYTHONBREAKPOINT' (boolean?), it would make sense (I _think_ so) to add a
condition parameter to the breakpoint() call. This does raise several
questions, but it seems that it could make for a simple unified way to
conditionally call an arbitrary debugger. What I found useful (in the
contecxt of ipython - but general enough) you can see in this gist:
If PEP 553's breakpoint() were to follow this sort of interface (with
"condition"), it raises a couple of questions:
- how would a missing (default) parameter be done?
- how would parameters to be passed to the debugger "of record" be passed
in (named tuple? - sort of ugly)
- would PYTHONBREAKPOINT be a global switch (I think yes), vs a `condition`
I have no dog in the fight, but to raise the possibility (?) of having PEP
553 implement simple conditional breakpoint processing.
Any / all comments much appreciated.
On Mon, Oct 2, 2017 at 7:06 PM, Barry Warsaw <barry at python.org> wrote:
> On Oct 2, 2017, at 18:43, Guido van Rossum <guido at python.org> wrote:
> > OK. That then concludes the review of your PEP. It is now accepted!
> Congrats. I am looking forward to using the backport. :-)
> Yay, thanks! We’ll see if I can sneak that backport past Ned. :)
> Python-Dev mailing list
> Python-Dev at python.org
> Unsubscribe: https://mail.python.org/mailman/options/python-dev/
-------------- next part --------------
An HTML attachment was scrubbed...
More information about the Python-Dev