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

Groups > comp.lang.python > #98026 > unrolled thread

Re: UNABLE TO GET IDLE TO RUN

Back to article view | Back to comp.lang.python

This discussion starts older than the indexed window; earlier articles aren't shown. The article labeled Started by below is the oldest one visible, not the original post.

Contents

  Re: UNABLE TO GET IDLE TO RUN Chris Angelico <rosuav@gmail.com> - 2015-11-01 12:59 +1100

#98026 — Re: UNABLE TO GET IDLE TO RUN

On Sun, Nov 1, 2015 at 12:45 PM, Michiel Overtoom <motoom@xs4all.nl> wrote:
> I'd go even a step further. I think IDLE should not only warn, but completely prevent saving a file which shadows a stdlib module, which will effectively render Python unusable. I remember from a few weeks back, a teacher with the same problem posted this on the mailinglist. Eventually she had a technician coming in to reinstall Windows, just to fix this problem ;-) What an overkill...
>

Trouble is, that applies only if Idle was the thing that saved it
under that name and in that location. And that still only prevents
access to one module (imagine, for instance, shadowing wave.py - how
many programs will really break?). Not sure it should *prevent*
anything like that. A warning, sure, but not an absolute error.

ChrisA

[toc] | [standalone]

Back to top | Article view | comp.lang.python

csiph-web