On Mon, Oct 17, 2011 at 8:55 AM, Sam Partington <sam.parting...@gmail.com>wrote:
> Yes it is a bit annoying to have to treat those specially, but other > than -c/-m it does not need to understand pythons args, just check > that the arg is not an explicit version specifier. -q/-Q etc have no > impact on how to treat the file. > > In fact there's no real need to treat -c differently as it's extremely > unlikely that there is a file that might match. But for -m you can > come up with a situation where if you it gets it wrong. e.g. 'module' > and 'module.py' in the cwd. > > I would suggest that it is also unlikely that there will be any future > options would need any special consideration. > What about -S (no site.py) and -E (no environment)? These are needed for secure setuid scripts on *nix; I don't know how often they'd be used in practice on Windows. (Basically, they let you isolate a script's effective sys.path; there may be some use case overlap with virtual envs.
_______________________________________________ Python-Dev mailing list Python-Dev@python.org http://mail.python.org/mailman/listinfo/python-dev Unsubscribe: http://mail.python.org/mailman/options/python-dev/archive%40mail-archive.com
