New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
IDLE: Detect Python files even if name doesn't end in .py #51053
Comments
A Python source file name doesn't necesarily end This patch makes IDLE recognize as a Python source http://permalink.gmane.org/ |
This makes sense, but the code should:
|
This new patch addresses the previous comments. |
I am a little puzzled by this issue.
Also, I believe there is another issue to add a 'Treat this as Python code' entry to one of the menus. This would cover the case of files without extensions and files that are not python files but happen (on a case-by-case basis) to have python code embedded within. So I am thinking that this should be closed. |
This is related to bpo-6858. I assume that the point of this issue is to enable syntax highlighting by relying on the Windows registry? |
I am also somewhat puzzled by this issue. |
Is the error message a traceback? If so, could you open a separate issue for it? |
No. When I try to open the file a small window entitled "Specify file encoding" pops up that says |
bpo-6858 was the issue I referred to. |
Note: these values reflect the state of the issue at the time it was migrated and might not reflect the current state.
Show more details
GitHub fields:
bugs.python.org fields:
The text was updated successfully, but these errors were encountered: