[issue28923] Nonexisting encoding specified in Tix.py

2017-03-31 Thread Donald Stufft
Changes by Donald Stufft : -- pull_requests: +997 ___ Python tracker ___ ___

[issue28923] Nonexisting encoding specified in Tix.py

2016-12-21 Thread Terry J. Reedy
Changes by Terry J. Reedy : -- resolution: -> fixed stage: patch review -> resolved status: open -> closed ___ Python tracker ___

[issue28923] Nonexisting encoding specified in Tix.py

2016-12-21 Thread Roundup Robot
Roundup Robot added the comment: New changeset eb8667196f93 by Terry Jan Reedy in branch '3.5': Issue 28923: Remove editor artifacts from Tix.py. https://hg.python.org/cpython/rev/eb8667196f93 New changeset 4a82412a3c51 by Terry Jan Reedy in branch '3.6': Issue 28923: Remove editor artifacts

[issue28923] Nonexisting encoding specified in Tix.py

2016-12-21 Thread Roundup Robot
Roundup Robot added the comment: New changeset ef03aff3b195 by Terry Jan Reedy in branch '2.7': Issue 28923: Remove editor artifacts from Tix.py, https://hg.python.org/cpython/rev/ef03aff3b195 -- nosy: +python-dev ___ Python tracker

[issue28923] Nonexisting encoding specified in Tix.py

2016-12-13 Thread Serhiy Storchaka
Serhiy Storchaka added the comment: Yes, CPython tokenizer recognizes encoding starting with "iso-latin-1-" as "iso-8859-1" (see get_normal_name() in Parser/tokenizer.c:228). I agreed that coding cookie or all line can be removed from Tix.py. Please do that. -- assignee: ->

[issue28923] Nonexisting encoding specified in Tix.py

2016-12-13 Thread Terry J. Reedy
Terry J. Reedy added the comment: Serhiy, if you agree with the proposed removal, but want me to do it, I will. -- ___ Python tracker ___

[issue28923] Nonexisting encoding specified in Tix.py

2016-12-13 Thread Terry J. Reedy
Terry J. Reedy added the comment: I reread https://docs.python.org/27/reference/lexical_analysis.html#encoding-declarations A first or second line must be a comment matching "coding[=:]\s*([-\w.]+)" (which IDLE uses) and the captured name "must be recognized by Python". I also did some

[issue28923] Nonexisting encoding specified in Tix.py

2016-12-13 Thread Ivan Pozdeev
Ivan Pozdeev added the comment: I'm more puzzled how noone has noticed this until now if it's supposed to produce an error upon compilation. (Well, it doesn't. I couldn't quite figure out how the encoding declaration is parsed, but it's clear the line _isn't_ matched as a regex like the docs

[issue28923] Nonexisting encoding specified in Tix.py

2016-12-12 Thread Terry J. Reedy
Terry J. Reedy added the comment: I am a little puzzled as to how a file rename changed the content, but the annotation history seems to show that. Anyway, ... When I load the file in IDLE 2.7, I get a warning. I am a bit surprised as this is not a proper encoding declaration. IDLE's re

[issue28923] Nonexisting encoding specified in Tix.py

2016-12-12 Thread Berker Peksag
Changes by Berker Peksag : -- nosy: +serhiy.storchaka, terry.reedy stage: -> patch review type: compile error -> behavior ___ Python tracker

[issue28923] Nonexisting encoding specified in Tix.py

2016-12-09 Thread Ivan Pozdeev
New submission from Ivan Pozdeev: $ head 'c:\Py\Lib\lib-tk\Tix.py' -n 1 # -*-mode: python; fill-column: 75; tab-width: 8; coding: iso-latin-1-unix -*- There's no "iso-latin-1-unix" encoding in Python, so this declaration produces an error in some code analysis tools (I have it in PyScripter),