On Sep 7, 2017, at 12:09, Fernando Perez <fperez....@gmail.com> wrote: >> The PEP has an open issue regarding breakpoint() taking *args and **kws, >> which would just be passed through the call stack. It sounds like you’d be >> in favor of that enhancement. > > If you go witht the `(*a, **k)` pass-through API, would you have a special > keyword-only arg called 'header' or similar? That seems like a decent > compromise to support the feature with the builtin while allowing other > implementations to offer more features. In any case, +1 to a pass-through > API, as long as the built-in supports some kind of mechanism to help the user > get their bearings with "you're here" type messages.
I don’t think I want to specify what goes in *args or **kws, I just want to pass them straight through. The user will have to have some understanding of what debugger they are using and what arguments their breakpoint hook allows. I’ll see what it takes to add `header` to pdb.set_trace(), but I’ll do that as a separate PR (i.e. not as part of this PEP). Cheers, -Barry
signature.asc
Description: Message signed with OpenPGP
_______________________________________________ Python-Dev mailing list Python-Dev@python.org https://mail.python.org/mailman/listinfo/python-dev Unsubscribe: https://mail.python.org/mailman/options/python-dev/archive%40mail-archive.com
