➜

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.

作者 belopolsky
收信人 Claudiu.Popa, belopolsky, eric.araujo, flox, pitrou
日期 2010-09-08.00:29:51
SpamBayes Score 3.8362323e-06
Marked as misclassified 否
Message-id <AANLkTinKczQg6JzRgr6hht5m_zM8K7g3e2_TVyvwnEyo@mail.gmail.com>
In-reply-to <1283904510.52.0.209826265325.issue9598@psf.upfronthosting.co.za>
内容
On Tue, Sep 7, 2010 at 8:08 PM, Éric Araujo <report@bugs.python.org> wrote:
..
> Why would it be the job of untabify to report invalid non-ASCII characters in C files?
>
Since untabify works by loading C code as text, it has to assume some
encoding.   Failing with uncaught decode error (as it currently does
on non UTF-8 source) is not very user friendly.  For example, the
diagnostic does not report the position of the offending character and
does not explain how to fix the source.
历史
日期 用户 动作 参数
2010-09-08 00:29:53belopolsky修改recipients: + belopolsky, pitrou, eric.araujo, flox, Claudiu.Popa
2010-09-08 00:29:52belopolsky链接issue9598 messages
2010-09-08 00:29:51belopolsky创建