A RetroSearch Logo

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

Search Query:

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

[Python-Dev] breakpoint() and $PYTHONBREAKPOINT

[Python-Dev] breakpoint() and $PYTHONBREAKPOINTBarry Warsaw barry at python.org
Mon Sep 11 20:27:13 EDT 2017
On Sep 10, 2017, at 13:46, Nathaniel Smith <njs at pobox.com> wrote:
> 
> 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.

Perhaps, but what would be the visible effects of that?  I.e. what would that buy you?

Cheers,
-Barry

-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 833 bytes
Desc: Message signed with OpenPGP
URL: <http://mail.python.org/pipermail/python-dev/attachments/20170911/fb67af00/attachment.sig>
More information about the Python-Dev mailing list

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