[issue21140] Idle: saving Shell or an OutputWindow should default to .txt

Terry J. Reedy added the comment: >From #45297, closed as duplicate. https://discuss.python.org/t/what-is-this-syntax-i-dont-know-how-to-fix-it/10844 -- ___ Python tracker

[issue21140] Idle: saving Shell or an OutputWindow should default to .txt

Terry J. Reedy added the comment: There was a recent stackoverflow question in which newbie pulled shell log into editor and ran as is. Got SyntaxError as 'Python 3' start of startup message. -- versions: +Python 3.10 -Python 3.6, Python 3.7 ___

[issue21140] Idle: saving Shell or an OutputWindow should default to .txt

Terry J. Reedy added the comment: A more drastic change would be to refuse to save OutputWindow and Shell as .py(w,o) files. #28365 is about a beginner who apparently save a short Shell session as .py, quit IDLE, loaded the saved session in an editor, and tried to run it. --

[issue21140] Idle: saving Shell or an OutputWindow should default to .txt

Terry J. Reedy added the comment: I am closing #28365 in favor of this. As noted there, Shell is a subclass of OutputWindow is a subclass of EditorWindow, so Shell should inherit new behavior from OutputWindow instead of both from EW. Change to the patch: I think .py should not even be a

[issue21140] Idle: saving Shell or an OutputWindow should default to .txt

Terry J. Reedy added the comment: In #11830 I suggested that Shell should be added to this issue. #26327 does the same, as the prompt and output are not code. At least in 3.x, these mixed code and text files should be encoded utf-8 (which is the same as ascii for all ascii files), as code