Kurt B. Kaiser added the comment:
I disagree. It's a major feature of the revised IDLE that code is
run
in a fresh environment every time. New users will only be
'surprised'
once, if at all. They will learn to put the creation of the
objects,
etc. that they want to retain into the top
Tal Einat added the comment:
First of all, installing Python on Windows creates a 'Edit with IDLE'
context-menu item whenever you right-click a .py file, which opens IDLE
without a subprocess. The reason for this is that there is still a
problem regarding having several instances of IDLE, each
Tal Einat added the comment:
I agree that the interface should be kept as simple as possible, but
this is a meaningful and important addition, which will help clarify to
the users how to work with the subprocess. The point of this change is
avoid surprising the user, while also making the
Kurt B. Kaiser added the comment:
I don't want to complicate the IDLE interface and confuse the users
with an additional decision (or a chording keypress for the normal
state) for this very special case (messing up a connection to a
robot). One of the main features of using the IDLE
Changes by Facundo Batista:
--
keywords: +patch
__
Tracker [EMAIL PROTECTED]
http://bugs.python.org/issue2049
__
___
Python-bugs-list mailing list
Unsubscribe:
New submission from Tal Einat:
When IDLE is run with a subprocess, add a 'Restart Shell Run Module'
item to the 'Run' menu in editor windows. Also add Alt-F5 as a hotkey
for this item.
This is what the 'Run Module' (F5) item used to do (when there was a
subprocess). As of this patch 'Run
Changes by Christian Heimes:
--
assignee: - kbk
priority: - normal
__
Tracker [EMAIL PROTECTED]
http://bugs.python.org/issue2049
__
___
Python-bugs-list mailing list
