Author belopolsky
Recipients belopolsky, brett.cannon, dmalcolm, eric.araujo, mark.dickinson, pitrou
Date 2010-08-13.22:56:29
SpamBayes Score 2.38858e-10
Marked as misclassified No
Message-id <1281740192.19.0.0770427429809.issue8912@psf.upfronthosting.co.za>
In-reply-to
Content
Note directly related to this issue, but untabify.py fails on files that contain non-ascii characters.  For example:

$ ./python.exe Tools/scripts/untabify.py Modules/_heapqmodule.c
Traceback (most recent call last):
    ...
    (result, consumed) = self._buffer_decode(data, self.errors, final)
UnicodeDecodeError: 'utf8' codec can't decode byte 0xe7 in position 173: invalid continuation byte


I am not sure what relevant C standard has to say about using non-ascii characters in comments, but the checking tool should not fail with a traceback in such situation.
History
Date User Action Args
2010-08-13 22:56:32belopolskysetrecipients: + belopolsky, brett.cannon, mark.dickinson, pitrou, eric.araujo, dmalcolm
2010-08-13 22:56:32belopolskysetmessageid: <1281740192.19.0.0770427429809.issue8912@psf.upfronthosting.co.za>
2010-08-13 22:56:30belopolskylinkissue8912 messages
2010-08-13 22:56:29belopolskycreate