RetroSearch Browse

Thu Sep 7 22:34:58 EDT 2017 · http://mail.python.org/pipermail/python-dev/2017-September/149346.html

On 7 September 2017 at 19:17, Barry Warsaw <barry at python.org> wrote:
> 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.

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   |   ncoghlan at gmail.com   |   Brisbane, Australia

Home - News ( United States | United Kingdom | Italy | Germany ) - Football scores

Showing content from http://mail.python.org/pipermail/python-dev/2017-September/149346.html below:

[Python-Dev] PEP 553 V2 - builtin breakpoint() (was Re: PEP 553: Built-in debug())