Re: UNABLE TO GET IDLE TO RUN

From	Chris Angelico <rosuav@gmail.com>
Newsgroups	comp.lang.python
Subject	Re: UNABLE TO GET IDLE TO RUN
Date	2015-11-01 12:59 +1100
Message-ID	<mailman.4.1446343201.4463.python-list@python.org> (permalink)
References	(15 earlier) <5A7F323C-ED4A-4CCA-A392-2C6F64EA6A6F@xs4all.nl> <201510301629.t9UGTY2i013568@fido.openend.se> <n114n1$o4h$1@ger.gmane.org> <n11lcd$snp$1@ger.gmane.org> <A8FC743A-822E-438E-A3CA-F27C5D3EE392@xs4all.nl>

Show all headers | View raw

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

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

Thread

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

csiph-web