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 sgrantham
Recipients Jim Fasarakis-Hilliard, ammar2, sgrantham
Date 2017-01-10.18:08:34
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <5f7220e5-6356-5ca8-e90a-77acb43776dc@walled.net>
In-reply-to <1484071097.33.0.954327019688.issue29226@psf.upfronthosting.co.za>
Content
My googling skills are a bit amiss too.  I searched for some kind of 
encoding pragma before reporting.  Perhaps just a footnote in the basic 
documentation of a python comment is the easiest solution.

Simon

On 1/10/2017 12:58 PM, Ammar Askar wrote:
> Ammar Askar added the comment:
>
> Thanks for the link Jim, looks like my googling skills are a bit amiss.
>
> I believe the reason the matching allows "encoding" is because a recommended format in the documentation is:
>
> # vim:fileencoding=<encoding-name>
>
> I think changing the behavior of the matching to be stricter and only match on "coding:" could result in breakages of such lines. Instead I think the error thrown could be more descriptive since I don't think it's too helpful.
>
> ----------
>
> _______________________________________
> Python tracker <report@bugs.python.org>
> <http://bugs.python.org/issue29226>
> _______________________________________
History
Date User Action Args
2017-01-10 18:08:34sgranthamsetrecipients: + sgrantham, ammar2, Jim Fasarakis-Hilliard
2017-01-10 18:08:34sgranthamlinkissue29226 messages
2017-01-10 18:08:34sgranthamcreate