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-July/067463.html below:

[Python-Dev] Handling of sys.args (Re: User's complaints)

[Python-Dev] Handling of sys.args (Re: User's complaints) [Python-Dev] Handling of sys.args (Re: User's complaints)Guido van Rossum guido at python.org
Sat Jul 15 16:45:37 CEST 2006
On 7/14/06, Nick Maclaren <nmm1 at cus.cam.ac.uk> wrote:
> "Guido van Rossum" <guido at python.org> wrote:
> >
> > OK, then I propose that we wait to see which things you end up having
> > to provide to sandboxed code, rather than trying to analyze it to
> > death in abstracto.
>
> However, the ORIGINAL proposal in this thread (to split off argv[0]
> and/or make that and the arguments read-only) is entirely different.
> That is purely a matter of convenience, cleanliness of specification
> or whatever you call it.  I can't imagine any good reason to separate
> argv[0] from argv[1:] by a sandbox (either way).

Sure. But that proposal has already been discussed (and found little
opposition). The thread then dispersed in a much less focused
discussion about the true purpose of the sys module..

-- 
--Guido van Rossum (home page: http://www.python.org/~guido/)
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