Simon Grantham added the comment: 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 <rep...@bugs.python.org> > <http://bugs.python.org/issue29226> > _______________________________________ ---------- _______________________________________ Python tracker <rep...@bugs.python.org> <http://bugs.python.org/issue29226> _______________________________________ _______________________________________________ Python-bugs-list mailing list Unsubscribe: https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
