[issue6804] IDLE: Detect Python files even if name doesn't end in .py

Change by Terry J. Reedy : -- versions: +Python 3.10 -Python 3.6, Python 3.7 ___ Python tracker ___ ___ Python-bugs-list mailing list

[issue6804] IDLE: Detect Python files even if name doesn't end in .py

Changes by Terry J. Reedy : -- assignee: -> terry.reedy versions: +Python 3.6, Python 3.7 -Python 2.7, Python 3.4, Python 3.5 ___ Python tracker ___ _

[issue6804] IDLE: Detect Python files even if name doesn't end in .py

Terry J. Reedy added the comment: #6858 was the issue I referred to. Recognizing #!...python, common on *nex, which the patch does not do, seems sensible. I thought about coding line, but general idea is not specific to python. -- stage: -> patch review versions: +Python 2.7, Python

[issue6804] IDLE: Detect Python files even if name doesn't end in .py

Daniel Swanson added the comment: No. When I try to open the file a small window entitled "Specify file encoding" pops up that says "The file's encoding is invalid in Python 3.x. Idle will convert it to UTF-8. What is the current encoding of the file?" followed by an entry widget that has "cp1

[issue6804] IDLE: Detect Python files even if name doesn't end in .py

Roger Serwy added the comment: Is the error message a traceback? If so, could you open a separate issue for it? -- ___ Python tracker ___

[issue6804] IDLE: Detect Python files even if name doesn't end in .py

Daniel Swanson added the comment: I am also somewhat puzzled by this issue. The other day I was able to open some .txt files just to see if I could and they opened just fine. Just now I tryed to open a .jpg file and I got an error message, but then again, why would someone save a python file a

[issue6804] IDLE: Detect Python files even if name doesn't end in .py

Roger Serwy added the comment: This is related to issue6858. I assume that the point of this issue is to enable syntax highlighting by relying on the Windows registry? -- nosy: +serwy ___ Python tracker __

[issue6804] IDLE: Detect Python files even if name doesn't end in .py

Terry J. Reedy added the comment: I am a little puzzled by this issue. 1. Why would a Windows user use any extention other than .py or .pyw, which IDLE opens fine. How many people do something senseless like hand-registering, say 'xiq', as a python file? 2. .pyc files are binary files and NOT

[issue6804] IDLE: Detect Python files even if name doesn't end in .py

Gabriel Genellina added the comment: This new patch addresses the previous comments. -- Added file: http://bugs.python.org/file15334/EditorWindow.diff ___ Python tracker ___

[issue6804] IDLE: Detect Python files even if name doesn't end in .py

Changes by Gabriel Genellina : Removed file: http://bugs.python.org/file14803/EditorWindow.diff ___ Python tracker ___ ___ Python-bugs-list mai

[issue6804] IDLE: Detect Python files even if name doesn't end in .py

Amaury Forgeot d'Arc added the comment: This makes sense, but the code should: - not make the query when the extension is empty - catch the WindowsError raised when the extension is not in the registry. -- nosy: +amaury.forgeotdarc ___ Python tracker

[issue6804] IDLE: Detect Python files even if name doesn't end in .py

New submission from Gabriel Genellina : A Python source file name doesn't necesarily end in .py/.pyw; on Linux, scripts usually have no extension but are recognized by its shebang line. Windows uses file type associations: .py files are of type Python.File, and .pyc files are Python.NoConFile