On Mon, Sep 11, 2017 at 11:03 AM, Barry Warsaw <barry at python.org> wrote: > On Sep 10, 2017, at 14:39, Chris Angelico <rosuav at 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
RetroSearch is an open source project built by @garambo | Open a GitHub Issue
Search and Browse the WWW like it's 1997 | Search results from DuckDuckGo
HTML:
3.2
| Encoding:
UTF-8
| Version:
0.7.4