Message115830
| Author |
belopolsky |
| Recipients |
Claudiu.Popa, belopolsky, eric.araujo, flox, pitrou |
| Date |
2010年09月08日.00:29:51 |
| SpamBayes Score |
3.8362323e-06 |
| Marked as misclassified |
No |
| Message-id |
<AANLkTinKczQg6JzRgr6hht5m_zM8K7g3e2_TVyvwnEyo@mail.gmail.com> |
| In-reply-to |
<1283904510.52.0.209826265325.issue9598@psf.upfronthosting.co.za> |
| Content |
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. |
|