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 pitrou
Recipients Arfrever, ezio.melotti, jcea, loewis, ned.deily, pitrou, ronaldoussoren, serhiy.storchaka, vstinner
Date 2012-05-09.18:41:16
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <1336588751.3382.0.camel@localhost.localdomain>
In-reply-to <>
> It would be good if someone checked on Macs work with command line
> arguments, including non-valid utf8. The difficulty is that you need
> to check on both Macs with 16-bit and with 32-bit wchar_t.

Actually, it should be enough to run the test suite, since we should
have tests for this.
As for different wchar_t widths, that's the kind of thing we can leave
to the buildbots (assuming our OS X buildbots come back alive some
day :-)).
Date User Action Args
2012-05-09 18:41:16pitrousetrecipients: + pitrou, loewis, jcea, ronaldoussoren, vstinner, ned.deily, ezio.melotti, Arfrever, serhiy.storchaka
2012-05-09 18:41:16pitroulinkissue14738 messages
2012-05-09 18:41:16pitroucreate