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

Groups > comp.lang.python > #98016 > 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 Terry Reedy <tjreedy@udel.edu> - 2015-10-31 01:59 -0400

#98016 — Re: UNABLE TO GET IDLE TO RUN

On 10/30/2015 9:15 PM, Terry Reedy wrote:
> On 10/30/2015 12:29 PM, Laura Creighton wrote:
>> In a message of Fri, 30 Oct 2015 16:21:30 +0100, Michiel Overtoom writes:
>>> Hi,
>>>
>>> Laura wrote:
>>>> I think that it would be useful if IDLE spit out a warning
>>>
>>> An ounce of prevention is worth a pound of cure. Maybe it's an idea
>>> that IDLE gives a warning when you're trying to save a file with a
>>> name that would shadow an existing module?
>
>> You might want to add that idea here:
>> https://bugs.python.org/issue25514

This is a different issue than IDLE avoiding clashes.  I opened
https://bugs.python.org/issue25522

> A warning requires a list to check against.  I just suggested on
> python-ideas the addition of a 'module' module, similar to the 'keyword'
> module, that would have the needed lists and functions.

Guido pointed me to sys.builtin_module_names, which is needed for the 
issue above.

-- 
Terry Jan Reedy

[toc] | [standalone]

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

csiph-web