[Python-Dev] PEP 553 V2 - builtin breakpoint() (was Re: PEP 553: Built-in debug())
Adrian Petrescu
apetresc at gmail.com
Thu Sep 7 23:02:52 EDT 2017
More information about the Python-Dev mailing list
Thu Sep 7 23:02:52 EDT 2017
- Previous message (by thread): [Python-Dev] PEP 553 V2 - builtin breakpoint() (was Re: PEP 553: Built-in debug())
- Next message (by thread): [Python-Dev] PEP 553 V2 - builtin breakpoint() (was Re: PEP 553: Built-in debug())
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
Would that not be a security concern, if you can get Python to execute arbitrary code just by setting an environment variable? On Thu, Sep 7, 2017 at 10:47 PM, Barry Warsaw <barry at python.org> wrote: > On Sep 7, 2017, at 19:34, Nick Coghlan <ncoghlan at gmail.com> wrote: > > > Now that you put it that way, it occurs to me that CI environments > > could set "PYTHONBREAKPOINTHOOK=sys:exit" to make breakpoint() an > > immediate failure rather than halting the CI run waiting for input > > that will never arrive. > > You better watch out Nick. You’re starting to sway me on adding the > environment variable. > > -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/ > apetresc%40gmail.com > > -------------- next part -------------- An HTML attachment was scrubbed... URL: <http://mail.python.org/pipermail/python-dev/attachments/20170907/e2ae1d8a/attachment.html>
- Previous message (by thread): [Python-Dev] PEP 553 V2 - builtin breakpoint() (was Re: PEP 553: Built-in debug())
- Next message (by thread): [Python-Dev] PEP 553 V2 - builtin breakpoint() (was Re: PEP 553: Built-in debug())
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
More information about the Python-Dev mailing list