[issue11838] IDLE: make interactive code savable as a runnable script

Terry J. Reedy added the comment: In #45297, Steven D'Aprano suggests deleting code immediately followed by traceback. (SyntaxErrors should not be there at all -- another issue.) But should NameError, for instance, be ignore, just because user printed something? Or block removed just beca

[issue11838] IDLE: make interactive code savable as a runnable script

Change by Terry J. Reedy : -- priority: normal -> high ___ Python tracker ___ ___ Python-bugs-list mailing list Unsubscribe: https:

[issue11838] IDLE: make interactive code savable as a runnable script

Terry J. Reedy added the comment: This should be easier to do with the new shell with indents fixed. -- nosy: -roger.serwy, tlesher versions: +Python 3.11 -Python 3.6, Python 3.7 ___ Python tracker

[issue11838] IDLE: make interactive code savable as a runnable script

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 ___

[issue11838] IDLE: make interactive code savable as a runnable script

Terry J. Reedy added the comment: #21140 is about saving Output Window (renamed) as .txt instead of .py. Same method should be used to save shell log as .txt. My idea is that File menu for shell window should, if possible, have both Save as log Save as runnable code -- __

[issue11838] IDLE: make interactive code savable as a runnable script

Changes by Terry J. Reedy : -- type: -> enhancement versions: +Python 2.7, Python 3.4, Python 3.5 -Python 3.3 ___ Python tracker ___

[issue11838] IDLE: make interactive code savable as a runnable script

Terry J. Reedy added the comment: Interesting example. This issue is a bit more complicated than I thought. Clearly, the call that reveals an error in previous lines should not be simply deleted. -- ___ Python tracker

[issue11838] IDLE: make interactive code savable as a runnable script

Roger Serwy added the comment: This issue relates to #1178 A traceback does not necessarily mean that the last statement had the error. For example: >>> a = lambda: 1/0 >>> a() Traceback (most recent call last): File "", line 1, in a() File "", line 1, in

[issue11838] IDLE: make interactive code savable as a runnable script

Terry J. Reedy added the comment: Either way, it would be nice to have erroneous commands flagged or filtered. That can be detected when the first line of output is Traceback (most recent call last): I typically would copy, correct, and rerun a line until I get it correct, so I would want b

[issue11838] IDLE: make interactive code savable as a runnable script

Roger Serwy added the comment: I considered saving directly from the shell but then I ran into a use-case problem. Saving the shell window as an runnable script will also save any syntax errors that were entered. A user would then have to open an editor to correct these errors. A high-level

[issue11838] IDLE: make interactive code savable as a runnable script

Terry J. Reedy added the comment: Roger Serway pointed me to the PastePyShell.py extension that is part of the IdleX package http://idlex.sourceforge.net/ That does the conversion when *pasting* interpreter text into an edit window. I would have File/Save do the same thing when saving the she

[issue11838] IDLE: make interactive code savable as a runnable script

Changes by Roger Serwy : -- nosy: +serwy ___ Python tracker ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org

[issue11838] IDLE: make interactive code savable as a runnable script

Changes by Tim Lesher : -- nosy: +tlesher ___ Python tracker ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.or

[issue11838] IDLE: make interactive code savable as a runnable script

Changes by Éric Araujo : -- nosy: +eric.araujo title: IDLE: make interactive code runnable. -> IDLE: make interactive code savable as a runnable script ___ Python tracker ___ __