[issue4126] remove not decodable environment variables

Martin v. Löwis added the comment: This patch is out of date with PEP 383 -- resolution: -> out of date status: open -> closed ___ Python tracker ___ ___

[issue4126] remove not decodable environment variables

Changes by Daniel Diniz : -- nosy: +loewis priority: -> high versions: +Python 3.1 -Python 3.0 ___ Python tracker ___ ___ Python-bugs-

[issue4126] remove not decodable environment variables

Toshio Kuratomi <[EMAIL PROTECTED]> added the comment: """ About your subprocess example: we choose to refuse it because we don't mix bytes (your non decodable PATH) and unicode ('myapp.sh') """ If python3 is doing things right we shouldn't be mixing bytes and unicode here: 1) the programmer is

[issue4126] remove not decodable environment variables

STINNER Victor <[EMAIL PROTECTED]> added the comment: About your subprocess example: we choose to refuse it because we don't mix bytes (your non decodable PATH) and unicode ('myapp.sh'). Using my patch in issue #4036 you will be able to run program with bytes arguments (including the program n

[issue4126] remove not decodable environment variables

Toshio Kuratomi <[EMAIL PROTECTED]> added the comment: Yep :-) I am against throwing away valid data just because we can't interpret it automatically. Environment variables in Unix hold bytes. Those bytes are usually ASCii characters, however, they do not have to be. This is a case of being o

[issue4126] remove not decodable environment variables

STINNER Victor <[EMAIL PROTECTED]> added the comment: See also issue #4006 which asks the opposite (keep invalid variables, even in os.environ(b)) :-) ___ Python tracker <[EMAIL PROTECTED]> __

[issue4126] remove not decodable environment variables

Changes by STINNER Victor <[EMAIL PROTECTED]>: Removed file: http://bugs.python.org/file11799/unsetenv.patch ___ Python tracker <[EMAIL PROTECTED]> ___

[issue4126] remove not decodable environment variables

STINNER Victor <[EMAIL PROTECTED]> added the comment: while+strcmp() in _Py_unsetenv() is useless since we already get the pointer to the evil variable. The new patch is shorter. Added file: http://bugs.python.org/file11800/unsetenv-2.patch ___ Python tracke

[issue4126] remove not decodable environment variables

STINNER Victor <[EMAIL PROTECTED]> added the comment: Note: I don't have Windows at home to test my patch on Windows. At least, the patch works correctly on Ubuntu Gutsy/i386. Example to demonstrate the issue: $ env -i a=a b=$(echo -e '--\xff--') c=c ./python -c "import os; os.execvp('/usr/bin

[issue4126] remove not decodable environment variables

New submission from STINNER Victor <[EMAIL PROTECTED]>: Python3 skips environment variables which can not be parsed and decoded as unicode strings. But exec*() functions keep the original environment and so the child process environment is different than the Python environement (than os.enviro