On Sep 5, 2017, at 19:31, Giampaolo Rodola' <g.rod...@gmail.com> wrote: > > True. Personally I have a shortcut in my IDE (Sublime) so I when I type "pdb" > -> TAB it auto completes it. > > Somehow I think debug() would make this a bit harder as it's more likely a > "debug()" line will pass unnoticed. > For this reason I would give a -1 to this proposal.
I think if your linter or editor can take note of the pdb idiom, it can also do so for the debug() built-in. > Personally I would find it helpful if there was a hook to choose the default > debugger to use on "pdb.set_trace()" via .pdbrc or PYTHONDEBUGGER environment > variable or something. > I tried (unsuccessfully) to run ipdb on "pdb.set_trace()", I gave up and > ended up emulating auto completion and commands history with this: > https://github.com/giampaolo/sysconf/blob/master/home/.pdbrc.py I don’t think that’s a good idea. pdb is a thing, and that thing is the standard library debugger. I don’t think ‘pdb’ should be the term we use to describe a generic Python debugger interface. That to me is one of the advantages of PEP 553; it separates the act of invoking the debugging from the actual debugger so invoked. 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
