Nick Coghlan added the comment:
I'd like to revisit this after PEP 432 is in place, since having to do this
dance for arg processing when running on Linux in the POSIX locale is somewhat
lame:
argv = sys.argv
encoding = locale.getpreferredencoding() # Hope nobody changed the locale!
fixed_encoding = read_encoding_from("/etc/locale.conf") # For example
argvb = [arg.encode(encoding, "surrogateescape") for arg in argv]
fixed_argv = [arg.decode(fixed_encoding, "surrogateescape") for arg in
argvb]
(For stricter parsing, leave out the second "surrogateescape")
Now, if PEP 432 resolves the system encoding issue such that we are able to use
the right encoding even when locale.getpreferredencoding() returns the wrong
answer, then it may not be worthwhile to also provide sys.argvb (especially
since it won't help hybrid 2/3 code). On the other hand, like os.environb, it
does make it easier for POSIX-only code paths that wants to handle boundary
encoding issues directly to stick with consuming the binary data directly and
avoid the interpreter's automatic conversion to the text domain.
Note also that os.environb is only available when os.supports_bytes_environ is
True, so it would make sense to only provide sys.argvb in the circumstances
where we provide os.environb.
----------
assignee: -> ncoghlan
nosy: +ncoghlan
resolution: wont fix -> later
status: closed -> open
versions: +Python 3.5 -Python 3.3
_______________________________________
Python tracker <[email protected]>
<http://bugs.python.org/issue8776>
_______________________________________
_______________________________________________
Python-bugs-list mailing list
Unsubscribe:
https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
