[Python-Dev] PEP 553; the interaction between $PYTHONBREAKPOINT and -E
Guido van Rossum
guido at python.org
Wed Oct 4 14:14:58 EDT 2017
Treating -E as PYTHONBREAKPOINT=0 makes sense.
On Wed, Oct 4, 2017 at 11:06 AM, Barry Warsaw <barry at python.org> wrote:
> Victor brings up a good question in his review of the PEP 553
> The question is whether $PYTHONBREAKPOINT should be ignored if -E is given?
> I think it makes sense for $PYTHONBREAKPOINT to be sensitive to -E, but in
> thinking about it some more, it might make better sense for the semantics
> to be that when -E is given, we treat it like PYTHONBREAKPOINT=0, i.e.
> disable the breakpoint, rather than fallback to the `pdb.set_trace` default.
> My thinking is this: -E is often used in production environments to
> prevent stray environment settings from affecting the Python process. In
> those environments, you probably also want to prevent stray breakpoints
> from stopping the process, so it’s more helpful to disable breakpoint
> processing when -E is given rather than running pdb.set_trace().
> If you have a strong opinion either way, please follow up here, on the PR,
> or on the bug tracker.
> Python-Dev mailing list
> Python-Dev at python.org
> Unsubscribe: https://mail.python.org/mailman/options/python-dev/
--Guido van Rossum (python.org/~guido)
-------------- next part --------------
An HTML attachment was scrubbed...
More information about the Python-Dev