Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]

Groups > comp.lang.python > #98027

Re: UNABLE TO GET IDLE TO RUN

Show all headers | View raw

On 10/31/2015 9:45 PM, Michiel Overtoom wrote:
>
>> On 31 Oct 2015, at 06:59, Terry Reedy <tjreedy@udel.edu> wrote:
>> This is a different issue than IDLE avoiding clashes.  I opened
>> https://bugs.python.org/issue25522
>
> Terry, thanks for recording this into the issue tracker.
>
> I'd go even a step further. I think IDLE should not only warn, but

The warning will require a choice, with the default (if one just hits 
<Enter>) being to reject the duplicate and go back to the Save-as 
dialog.  Please add yourself as nosy on the issue so you can comment on 
the message whenever I get around to adding a patch.

> completely prevent saving a file which shadows a stdlib module, which
> will effectively render Python unusable.

That is too authoritarian for Python.  As Chris noted, all I can do with 
IDLE patches is improve the situation, not solve it.

> I remember from a few weeks
> back, a teacher with the same problem posted this on the mailinglist.

That involved the additional problem of the working directory being 
/windows/system32.  This was fixed today for 3.5.1.

> Eventually she had a technician coming in to reinstall Windows, just
> to fix this problem ;-) What an overkill...

If her classroom budget was not charged for that, that may have been the 
cheapest solution *for her*, though not for the school or whoever paid 
the tech.
-- 
Terry Jan Reedy

Back to comp.lang.python | Previous | Next — Next in thread | Find similar | Unroll thread

Thread

Re: UNABLE TO GET IDLE TO RUN Terry Reedy <tjreedy@udel.edu> - 2015-10-31 22:50 -0400
  Re: UNABLE TO GET IDLE TO RUN Steven D'Aprano <steve@pearwood.info> - 2015-11-02 01:41 +1100

csiph-web