A RetroSearch Logo

Home - News ( United States | United Kingdom | Italy | Germany ) - Football scores

Search Query:

Showing content from https://mail.python.org/pipermail/python-dev/2006-June/066633.html below:

[Python-Dev] doc for new restricted execution design for Python

[Python-Dev] doc for new restricted execution design for Python [Python-Dev] doc for new restricted execution design for PythonJim Jewett jimjjewett at gmail.com
Tue Jun 27 19:06:27 CEST 2006
On 6/27/06, Brett Cannon <brett at python.org> wrote:
> My worry with this is that by providing checking functions that just return
> true or false that people will rely on those too much and have logic errors
> in their check and let security holes develop.  That is why the checking
> functions as they stand now are macros that do the error return for you.

Using a macro that returns an Error is OK.  (Well, from this
perspective; it might be a problem for reference leaks.)

I just want a single call that does my erroring out, instead of two
separate calls depending on whether the interpreter is trusted.

-jJ
More information about the Python-Dev mailing list

RetroSearch is an open source project built by @garambo | Open a GitHub Issue

Search and Browse the WWW like it's 1997 | Search results from DuckDuckGo

HTML: 3.2 | Encoding: UTF-8 | Version: 0.7.4