On 7 September 2017 at 19:17, Barry Warsaw <ba...@python.org> wrote: > On Sep 7, 2017, at 18:12, Nick Coghlan <ncogh...@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.
Now that you put it that way, it occurs to me that CI environments could set "PYTHONBREAKPOINTHOOK=sys:exit" to make breakpoint() an immediate failure rather than halting the CI run waiting for input that will never arrive. Cheers, Nick. -- Nick Coghlan | ncogh...@gmail.com | Brisbane, Australia _______________________________________________ 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
