This issue tracker has been migrated to GitHub, and is currently read-only.
For more information, see the GitHub FAQs in the Python's Developer Guide.

Author vstinner
Recipients ezio.melotti, pitrou, python-dev, serhiy.storchaka, vstinner
Date 2012-11-11.22:15:48
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <1352672148.21.0.589310476134.issue16444@psf.upfronthosting.co.za>
In-reply-to
Content
> I suppose you noticed you broke a bunch of buildbots :)

Failures occur on FreeBSD, OpenIndiana and some other buildbots which don't set a locale and so use the "C" locale. main() decodes command line arguments from the locale encoding using _Py_char2wchar(). On these OSes, the "C" locale uses the ISO-8859-1 encoding, but the problem is that nl_langinfo(CODESET) announces ASCII :-/ test_cmd_line.test_undecodable_code() handles this case. Extract of a comment:

# _Py_char2wchar() decoded b'\xff' as '\xff' even if the locale is  
# C and the locale encoding is ASCII. It occurs on FreeBSD, Solaris 
# and Mac OS X.                                                     

Mac OS X is now using UTF-8 to decode the command line arguments.

I just created the issue #16455 to fix FreeBSD and OpenIndiana.

I propose to close this issue because I consider it as fixed (#16455 will reenable TESTFN_UNDECODABLE in test_cmd_line_script).
History
Date User Action Args
2012-11-11 22:15:48vstinnersetrecipients: + vstinner, pitrou, ezio.melotti, python-dev, serhiy.storchaka
2012-11-11 22:15:48vstinnersetmessageid: <1352672148.21.0.589310476134.issue16444@psf.upfronthosting.co.za>
2012-11-11 22:15:48vstinnerlinkissue16444 messages
2012-11-11 22:15:48vstinnercreate