This issue tracker has been migrated to GitHub, and is currently read-only.
For more information, see the GitHub FAQs in the Python's Developer Guide.

Author terry.reedy
Recipients eric.araujo, terry.reedy
Date 2021-09-27.06:31:28
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <>
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 because it comes before print statement?

Without more feedback, I believe most would want all code actually run.  If there is a Traceback, Add comment with error and message.

UI is a tough issue.  I don't want to add more File menu entries and hot keys.  We can add to shell context menu as have already done.

Maybe this: after getting the save name, branch on type: .py, code only; anything else, full log. Subsequent ^S saves use last save-as name to decide.
Date User Action Args
2021-09-27 06:31:28terry.reedysetrecipients: + terry.reedy, eric.araujo
2021-09-27 06:31:28terry.reedysetmessageid: <>
2021-09-27 06:31:28terry.reedylinkissue11838 messages
2021-09-27 06:31:28terry.reedycreate