[Python-Dev] PEP 553; the interaction between $PYTHONBREAKPOINT and -E

Guido van Rossum guido at python.org
Wed Oct 4 17:03:32 EDT 2017


Well that also makes sense.

On Wed, Oct 4, 2017 at 1:52 PM, Antoine Pitrou <solipsis at pitrou.net> wrote:

> On Wed, 4 Oct 2017 14:06:48 -0400
> Barry Warsaw <barry at python.org> wrote:
> > Victor brings up a good question in his review of the PEP 553
> implementation.
> >
> > https://github.com/python/cpython/pull/3355
> > https://bugs.python.org/issue31353
> >
> > 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.
>
> """Special cases aren't special enough to break the rules."""
>
> People expect -E to disable envvar-driven overrides, so just treat it
> like that and don't try to second-guess the user.
>
> Regards
>
> Antoine.
>
>
> _______________________________________________
> Python-Dev mailing list
> Python-Dev at python.org
> https://mail.python.org/mailman/listinfo/python-dev
> Unsubscribe: https://mail.python.org/mailman/options/python-dev/
> guido%40python.org
>



-- 
--Guido van Rossum (python.org/~guido)
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mail.python.org/pipermail/python-dev/attachments/20171004/b9ee6414/attachment.html>


More information about the Python-Dev mailing list