[Python-Dev] doc for new restricted execution design for Python
Jim Jewett
jimjjewett at gmail.com
Tue Jun 27 19:06:27 CEST 2006
More information about the Python-Dev mailing list
Tue Jun 27 19:06:27 CEST 2006
- Previous message: [Python-Dev] doc for new restricted execution design for Python
- Next message: [Python-Dev] doc for new restricted execution design for Python
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
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
- Previous message: [Python-Dev] doc for new restricted execution design for Python
- Next message: [Python-Dev] doc for new restricted execution design for Python
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
More information about the Python-Dev mailing list