[issue23666] Add shell session logging option to IDLE

[Terry J. Reedy]

Terry J. Reedy  added the comment:

A dirty editor must be saved before running, or discarded before closing.  
Neither is true for Shell,  Making these at least an option in Shell should be 
the first change.  If the user has specified a savefile name, that should be 
used, and the user is responsible for the file.  If a file is automatically 
put, say, in .idlerc/shell.bak.py, there is an issue of when to delete or 
overwrite.

We should continue working to make automatic, versus explicit, shell logging 
less necessary.

If IDLE running in normal mode (user code running in a separate process) either 
closes by itself or locks up so that it *must* be closed, that should indicates 
a bug in python or IDLE that should be fixed.  There might be a couple such 
bugs left, I am not sure.

If the user process closes, the shell should restart one automatically. As far 
as I know, it dies.

If the user process hangs, control-C (Shell => Interrupt Execution) usually 
works,
  >>> while 1: 2+2
  KeyboardInterrupt
  >>> 
But a) beginning computer user may not know about ^C, or it may not work due to 
limitations in Python.  (There is an issue about the latter.)  In the latter 
case, one can restart with Shell => Restart Shell, but this is IDLE specific 
and users may not know about it.

When the shell catches ^C, it could create an after callback with a delay of, 
say, .5 seconds (but to be determined).  If ^C works, cancel the callback.  If 
not, display a message (only once per session) about using Restart.  Maybe next 
time, do an auto restart.

We might also think about detecting a hang (5 seconds, no output?) and printing 
a message about using ^C.

--
assignee:  -> terry.reedy
stage:  -> test needed
versions: +Python 3.7, Python 3.8, Python 3.9 -Python 3.5

___
Python tracker 

___
___
Python-bugs-list mailing list
Unsubscribe: 
https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com

[issue23666] Add shell session logging option to IDLE

[Tal Einat]

Tal Einat  added the comment:

I'm happy to look into implementing this. Also perhaps auto-saved backups for 
edited files.

Where would you suggest the files be kept? The user's .idlerc directory?

--
nosy: +taleinat

___
Python tracker 

___
___
Python-bugs-list mailing list
Unsubscribe: 
https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com

[issue23666] Add shell session logging option to IDLE

[Grant Jenks]

Grant Jenks added the comment:

+1 from me. I'd like to see it ask me to save when I close the window if I've 
already saved once.

--
nosy: +grantjenks

___
Python tracker 

___
___
Python-bugs-list mailing list
Unsubscribe: 
https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com

[issue23666] Add shell session logging option to IDLE

[Terry J. Reedy]

Terry J. Reedy added the comment:

I do not see how Restart (as opposed to a proposed Clear option) loses 
anything.  However, closing without saving definitely anything since a save.  
Moreover, even after saving Shell once, there is no Save on Close box displayed 
(as for editor windows) when closing Shell without saving.  This has been 
discussed somewhere (maybe StackOverflow) but I do not find an issue.

Raymond, would it be sufficient if saving once would mean that one could not 
close (or clear the window) without being prompted to save again?  What if we 
add timed autosaves #21152 (based on your comment on #21140, msg215485), or 
autosave (or autoappend) with each prompt?

--
nosy: +terry.reedy

___
Python tracker rep...@bugs.python.org
http://bugs.python.org/issue23666
___
___
Python-bugs-list mailing list
Unsubscribe: 
https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com

[issue23666] Add shell session logging option to IDLE

[Raymond Hettinger]

Raymond Hettinger added the comment:

Autosave would suffice.  :-)

The restart issue wasn't the usual restart you get by pressing F5.  What is 
happening is that someone does an action that kills or hangs the IDLE app, then 
they have to force close and restart IDLE itself.

--

___
Python tracker rep...@bugs.python.org
http://bugs.python.org/issue23666
___
___
Python-bugs-list mailing list
Unsubscribe: 
https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com

[issue23666] Add shell session logging option to IDLE

[Terry J. Reedy]

Terry J. Reedy added the comment:

Do you know if, when a process is killed, date written to open files gets 
flushed to disk?

--

___
Python tracker rep...@bugs.python.org
http://bugs.python.org/issue23666
___
___
Python-bugs-list mailing list
Unsubscribe: 
https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com

[issue23666] Add shell session logging option to IDLE

[Raymond Hettinger]

New submission from Raymond Hettinger:

IDLE's interactive shell supports File / Save to save an interactive session.  
However, if a user restarts a session or accidentally exits without saving, all 
is lost.

In Python courses I've taught, there has been a recurring request for an 
auto-logging feature (save the session at some regular interval).  This would 
help user's record everything they type during a Python class.

I suggest an addition to the File menu (for the interactive shell only): 
Session Logging Enable/Disable.

--
components: IDLE
messages: 238109
nosy: rhettinger
priority: normal
severity: normal
status: open
title: Add shell session logging option to IDLE
type: enhancement
versions: Python 3.5

___
Python tracker rep...@bugs.python.org
http://bugs.python.org/issue23666
___
___
Python-bugs-list mailing list
Unsubscribe: 
https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com