Yup. Using IDLE on Python 2.7 on a Mac, cmd-Q (or the corresponding menu option, for that matter), there is no prompt to save unsaved files. I hope someone more knowledgeable than me about IDLE can find the problem, or maybe just suggest where I should look. I'll keep looking, but as I said, I'm baffled that I can't even identify what code gets executed upon pressing cmd-Q.
I'll go ahead and prepare a patch for idle for Python 2.7 right away that won't have a fix for this serious save problem. The save issue can be considered separately. Bruce Sherwood On Thu, Oct 14, 2010 at 9:22 AM, Bruce Sherwood <bashe...@ncsu.edu> wrote: > I will submit an appropriate patch for 2.7; vidle was used with 2.6 > and 2.7 since summer 2009. There were indeed a variety of problems > with idlelib on Python 2 that the temporary fix of vidle addressed. I > wasn't aware that things got worse from 2.6 to 2.7, because I only > used vidle with these Pythons. > > I need to check whether the Mac failure to save changes upon pressing > cmd-Q was present in 2.7 as well as 3. > > Bruce Sherwood > > On Thu, Oct 14, 2010 at 8:57 AM, Guido van Rossum <gu...@python.org> wrote: >> Is there any chance of getting these changes into 2.7 as well? There >> will be bugfix updates for 2.7, and David Beazley just tweeted about >> how the IDLE experience with Python 2.7 got much worse compared to >> 2.6. >> >> -- >> --Guido van Rossum (python.org/~guido) >> _______________________________________________ >> IDLE-dev mailing list >> IDLE-dev@python.org >> http://mail.python.org/mailman/listinfo/idle-dev >> > _______________________________________________ IDLE-dev mailing list IDLE-dev@python.org http://mail.python.org/mailman/listinfo/idle-dev
