[issue1668] -E command line parameter intent

2008-01-07 Thread Georg Brandl
Georg Brandl added the comment: Committed getenv.2.diff and extended envvar docs in r59827. -- resolution: - accepted status: open - closed __ Tracker [EMAIL PROTECTED] http://bugs.python.org/issue1668 __

[issue1668] -E command line parameter intent

2008-01-06 Thread Georg Brandl
Georg Brandl added the comment: This is a documentation issue, it seems. The new command-line document already says only PYTHON* vars are ignored. -- components: +Documentation -Interpreter Core nosy: +georg.brandl versions: +Python 2.6 __ Tracker [EMAIL

[issue1668] -E command line parameter intent

2008-01-06 Thread Guido van Rossum
Guido van Rossum added the comment: To resolve this, how about this patch (getenv.2.diff)? - change getenv(PYTHONCASEOK) - Py_GETENV() (inside #ifdef PYOS_OS2) - rename THREADDEBUG - PYTHONTHREADDEBUG and use Py_GETENV() Added file: http://bugs.python.org/file9081/getenv.2.diff

[issue1668] -E command line parameter intent

2007-12-20 Thread Guido van Rossum
Guido van Rossum added the comment: I believe its original intent was to only ignore variables starting with PYTHON, but I'm not 100% sure. Ignoring PATH seems counterintuitive. I'm not sure about THREADDEBUG -- I'm thinking that variable should be renamed PYTHONTHREADDEBUG? BTW, doesn't this

[issue1668] -E command line parameter intent

2007-12-19 Thread Joseph Armbruster
New submission from Joseph Armbruster: url: http://svn.python.org/projects/python/branches/py3k rev: 59577 The intent of the -E command line parameter is not entirely clear from it's description. If it implies that All environment variables will be ignored then this is not currently the case.