Antoine Pitrou pit...@free.fr added the comment:
I think that we should accept that b'\xff' can be decoded as '\xff' and
that's all.
What do you plan to do to fix this failure?
==
FAIL: test_undecodable_env
STINNER Victor victor.stin...@haypocalc.com added the comment:
With r85466+r85467, the test_undecodable_env (of test_subprocess) uses C locale
to get ASCII locale encoding (for the first test, on unicode environment
variables). It should have the same effect than env['PYTHONFSENCODING'] =
STINNER Victor victor.stin...@haypocalc.com added the comment:
Ok, the issue is not complelty fixed ;-)
12:55 py-bb build #504 of x86 debian parallel 3.x is complete: Success
[build successful] Build details are at
STINNER Victor victor.stin...@haypocalc.com added the comment:
I tried... the issue is *now* complelty fixed
--
___
Python tracker rep...@bugs.python.org
http://bugs.python.org/issue9992
___
Changes by Éric Araujo mer...@netwok.org:
--
nosy: +eric.araujo
title: Command line arguments are not correctly decodediflocale and fileystem
encodingsaredifferent - Command-line arguments are not correctly decoded if
locale and fileystem encodings are different
STINNER Victor victor.stin...@haypocalc.com added the comment:
I commited issue9992.patch as r85430 (remove PYTHONFSENCODING) + r85435 (OSX:
decode command line arguments from utf-8).
These commits should fix this issue. Reopen the issue if you notice new
problems, or if the problem is not
STINNER Victor victor.stin...@haypocalc.com added the comment:
test_undecodable_env() of test_subprocess fails. r85430 removes the following
code which was added by Antoine to fix this issue.
# Force surrogate-escaping of \xFF in the child process;
# otherwise it can be decoded as-is if the
Marc-Andre Lemburg m...@egenix.com added the comment:
STINNER Victor wrote:
New submission from STINNER Victor victor.stin...@haypocalc.com:
On UNIX/BSD systems, Python decodes arguments with the locale encoding,
whereas subprocess encodes arguments with the fileystem encoding. If both
New submission from STINNER Victor victor.stin...@haypocalc.com:
On UNIX/BSD systems, Python decodes arguments with the locale encoding, whereas
subprocess encodes arguments with the fileystem encoding. If both encodings are
differents, we have a problem.
There was already the issue #4388 but
Changes by Philip Jenvey pjen...@underboss.org:
--
nosy: +pjenvey
___
Python tracker rep...@bugs.python.org
http://bugs.python.org/issue9992
___
___
Python-bugs-list
STINNER Victor victor.stin...@haypocalc.com added the comment:
[cmdline_encoding-2.patch] Patch to use locale encoding to decode and encode
command line arguments. Remarks about the patch:
- failing to get the locale encoding (very unlikely) is a fatal error
- TODO: in initfsencoding(),
11 matches
Mail list logo
