[Python-Dev] PEP 553; the interaction between $PYTHONBREAKPOINT and -E (original) (raw)

Victor Stinner victor.stinner at gmail.com
Thu Oct 5 02:58:44 EDT 2017

I concur with Antoine, please don't add a special case for -E. But it seems like you already agreed with that :-)

Victor

Le 5 oct. 2017 05:33, "Barry Warsaw" <barry at python.org> a écrit :

On Oct 4, 2017, at 21:52, Nick Coghlan <ncoghlan at gmail.com> wrote: > >> Unfortunately we probably won’t really get a good answer in practice until Python 3.7 is released, so maybe I just choose one and document that the behavior of PYTHONBREAKPOINT under -E is provision for now. If that’s acceptable, then I would just treat -E for PYTHONBREAKPOINT the same as all other environment variables, and we’ll see how it goes. > > I'd be fine with this as the main reason I wanted PYTHONBREAKPOINT=0 > was for pre-merge CI systems, and those tend to have tightly > controlled environment settings, so you don't need to rely on -E or -I > when running your tests. > > That said, it may also be worth considering a "-X nobreakpoints" > option (and then -I could imply "-E -s -X nobreakpoints").

Thanks for the feedback Nick. For now we’ll go with the standard behavior of -E and see how it goes. We can always add a -X later. Cheers, -Barry

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/ victor.stinner%40gmail.com -------------- next part -------------- An HTML attachment was scrubbed... URL: <http://mail.python.org/pipermail/python-dev/attachments/20171005/e2df77b5/attachment.html>

More information about the Python-Dev mailing list