Barry Warsaw barry at python.org
Sun Sep 10 21:03:58 EDT 2017

• Previous message (by thread): [Python-Dev] PEP 559 - built-in noop()
• Next message (by thread): [Python-Dev] PEP 559 - built-in noop()
• Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]

---

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`.

Cheers,
-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/20170910/a178a548/attachment.sig>

---

• Previous message (by thread): [Python-Dev] PEP 559 - built-in noop()
• Next message (by thread): [Python-Dev] PEP 559 - built-in noop()
• Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]

---

More information about the Python-Dev mailing list