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)
_
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 Pytho
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 ba
In article
,
Guido van Rossum 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.
In his tweet he is referring to Python 2
In article
,
Bruce Sherwood wrote:
> 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
At Ned Deily's suggestion I've posted the following to bugs.python.org:
It has just been discovered that at least since Python 2.6 on the Mac,
quitting IDLE does not prompt to save unsaved code, which is then
lost. The recently submitted diff for bringing Guilherme Polo's Google
Summer of Code imp
On 10/14/2010 10:57 AM, Guido van Rossum 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.
If there are new features in the patc
Ned Deily's note (repeated here) made me think that I should not
submit a patch for 2.7 because he has reason to believe that the
problems aren't with IDLE.
Bruce Sherwood
In article
,
Guido van Rossum wrote:
> Is there any chance of getting these chang
I'm trying to find out why when you quit on the Mac unsaved changes
don't trigger an invitation to save the file. Instead, IDLE quits and
you lose your edits.
There is code to bind cmd-q to the edit window and, on the Mac, to the
Tk root, through macosxSupport.setupApp which calls macosxSupport
ov
In article
,
Bruce Sherwood wrote:
> I'm trying to find out why when you quit on the Mac unsaved changes
> don't trigger an invitation to save the file. Instead, IDLE quits and
> you lose your edits.
>
> There is code to bind cmd-q to the edit window and, on the Mac, to the
> Tk root, through
In article
,
Bruce Sherwood wrote:
> Ned Deily's note (repeated here) made me think that I should not
> submit a patch for 2.7 because he has reason to believe that the
> problems aren't with IDLE.
I think the question of whether Guilherme's enhancements should go into
2.7 is independent of t
I'm relieved to hear that you may have a way to override. Yes, let's
continue the discussion in the bug report context.
Bruce Sherwood
On Thu, Oct 14, 2010 at 11:14 PM, Ned Deily wrote:
> In article
> ,
> Bruce Sherwood wrote:
>
>> I'm trying to find out why when you quit on the Mac unsaved ch
I'm quite happy to prepare a patch for 2.7; one possibility is to make
a diff from the 2.7 version of vidle. I guess I misinterpreted your
comments about 32/64 etc. I'll be out of touch for the next couple
days. I'm really excited about a two-day visit to Zuni Pueblo (New
Mexico).
Bruce Sherwood
13 matches
Mail list logo
