[Python-Dev] PEP 553; the interaction between $PYTHONBREAKPOINT and -E (original) (raw)
Barry Warsaw barry at python.org
Thu Oct 5 17:27:49 EDT 2017
- Previous message (by thread): [Python-Dev] PEP 553; the interaction between $PYTHONBREAKPOINT and -E
- Next message (by thread): [Python-Dev] PEP 544
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
I don't know what is the best option, but I dislike adding two options, PYTHONBREAKPOINT and -X nobreakpoint, for the same features. I would become complicated to know which option has the priority.
Just to close the loop, I’ve landed the PEP 553 PR treating PYTHONBREAKPOINT the same as all other environment variables when -E is present. Let’s see how that goes.
Thanks all for the great feedback and reviews. Now I’m thinking about putting a backport version on PyPI. :)
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/20171005/41effdd6/attachment.sig>
- Previous message (by thread): [Python-Dev] PEP 553; the interaction between $PYTHONBREAKPOINT and -E
- Next message (by thread): [Python-Dev] PEP 544
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]