[Python-Dev] PEP 553 V2 - builtin breakpoint() (was Re: PEP 553: Built-in debug())
Barry Warsaw
barry at python.org
Thu Sep 7 22:17:29 EDT 2017
More information about the Python-Dev mailing list
Thu Sep 7 22:17:29 EDT 2017
- Previous message (by thread): [Python-Dev] PEP 553 V2 - builtin breakpoint() (was Re: PEP 553: Built-in debug())
- Next message (by thread): [Python-Dev] PEP 553 V2 - builtin breakpoint() (was Re: PEP 553: Built-in debug())
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
On Sep 7, 2017, at 18:12, Nick Coghlan <ncoghlan at gmail.com> wrote: > > Related to this is the suggestion that we make the default > sys.breakpointhook() a no-op, so that accidentally checking in calls > to breakpoint() won' t hang CI systems. > > Then folks that wanted to use the functionality would set > "PYTHONBREAKPOINTHOOK=pdb:set_trace" I’d rather do it the other way ‘round because I want it to Just Work for the average developer, and maintainers of CI or production systems should be able to fairly easily tweak their environments to noop breakpoint(). Although maybe we want a shortcut for that, e.g. PYTHONBREAKPOINTHOOK=0 or some such. (Note, I’m still not sure it’s worth supporting the environment variable, but I am interesting in collecting the feedback on it.) -Barry -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 273 bytes Desc: Message signed with OpenPGP URL: <http://mail.python.org/pipermail/python-dev/attachments/20170907/cf1e1994/attachment.sig>
- Previous message (by thread): [Python-Dev] PEP 553 V2 - builtin breakpoint() (was Re: PEP 553: Built-in debug())
- Next message (by thread): [Python-Dev] PEP 553 V2 - builtin breakpoint() (was Re: PEP 553: Built-in debug())
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
More information about the Python-Dev mailing list