Nathaniel Smith njs at pobox.com
Sun Sep 10 16:46:14 EDT 2017

• Previous message (by thread): [Python-Dev] breakpoint() and $PYTHONBREAKPOINT
• Next message (by thread): [Python-Dev] breakpoint() and $PYTHONBREAKPOINT
• Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]

---

On Sun, Sep 10, 2017 at 12:06 PM, Barry Warsaw <barry at python.org> wrote:
> For PEP 553, I think it’s a good idea to support the environment variable $PYTHONBREAKPOINT[*] but I’m stuck on a design question, so I’d like to get some feedback.
>
> Should $PYTHONBREAKPOINT be consulted in breakpoint() or in sys.breakpointhook()?

Wouldn't the usual pattern be to check $PYTHONBREAKPOINT once at
startup, and if it's set use it to initialize sys.breakpointhook()?
Compare to, say, $PYTHONPATH.

-n

-- 
Nathaniel J. Smith -- https://vorpus.org

---

• Previous message (by thread): [Python-Dev] breakpoint() and $PYTHONBREAKPOINT
• Next message (by thread): [Python-Dev] breakpoint() and $PYTHONBREAKPOINT
• Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]

---

More information about the Python-Dev mailing list