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 taleinat
Recipients
Date 2007-07-20.23:29:28
SpamBayes Score
Marked as misclassified
Message-id
In-reply-to
Content
I agree with KBK that what you suggest goes against IDLE's philosophy, which is to be simple and uncluttered, avoiding "bells and whistles".

However, I do think that a simple "revert file" menu item in the File menu, which would just reload the file from the file system, could be generally useful.

Additionally, IDLE could monitor the file on the file system, and if it is changed outside of IDLE, ask the user whether to continue with the current version or switch to the new version on disk. I've seen some text editors do this, and it can save some headaches. Drawbacks are that some users may find this annoying (at least at first), and it could be somewhat complex to implement. Thoughts on this? Perhaps this should be brought up on IDLE-dev?

Each of the above would allow you to revert/merge using whatever CVS/SVN/etc. tools you normally use, then just load the new version inside the already open instance of IDLE. I think this would be a good separation of roles between IDLE and version control tools.
History
Date User Action Args
2007-08-23 16:12:50adminlinkissue1721083 messages
2007-08-23 16:12:50admincreate