On Mon, Sep 11, 2017 at 11:03 AM, Barry Warsaw <ba...@python.org> wrote: > On Sep 10, 2017, at 14:39, Chris Angelico <ros...@gmail.com> wrote: >> >> As a language change, definitely not. But I like this idea for >> PYTHONBREAKPOINT. You set it to the name of a function, or to "pass" >> if you want nothing to be done. It's a special case that can't >> possibly conflict with normal usage. > > I have working code for `PYTHONBREAKPOINT=0` and `PYTHONBREAKPOINT= ` (i.e. > the empty string as given by getenv()) meaning “disable”. I don’t think we > also need `PYTHONBREAKPOINT=pass`. >
Blank is the other one that I would stumble to. Works for me. ChrisA _______________________________________________ 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
