Re: subprocess startup error

From	Terry Reedy <tjreedy@udel.edu>
Newsgroups	comp.lang.python
Subject	Re: subprocess startup error
Date	2016-02-27 03:38 -0500
Message-ID	<mailman.166.1456562333.20994.python-list@python.org> (permalink)
References	(1 earlier) <CAFW38mHJDNsD48zbiyo3pXMpJJhPSjPvvwCij0-VjozDSuFscw@mail.gmail.com> <napk16$oi5$1@ger.gmane.org> <CAHVvXxRwmaejwnLMXZ-YTqVC=d7PAKABpxrTA3gY9tKmB-dE9Q@mail.gmail.com> <napp5f$d37$1@ger.gmane.org> <56D06A61.3030008@biologie.uni-freiburg.de>

Show all headers | View raw

On 2/26/2016 10:08 AM, Wolfgang Maier wrote:
> On 26.02.2016 15:57, Emile van Sebille wrote:
>> On 2/26/2016 6:49 AM, Oscar Benjamin wrote:
>>> On 26 February 2016 at 13:30, Peter Otten <__peter__@web.de> wrote:
>>>> Shweta Dinnimani wrote:
>>>>> i saved my file as string.py since than i'm facing this error
>>>>
>>>> Rename that file to something that does not clash with the module
>>>> names in
>>>> the standard library, mystring.py for example, and IDLE should work
>>>> again.
>>>
>>> It's ridiculous that it's this easy to accidentally crash IDLE and the
>>> Python shell.
>>
>> I don't think there's a way to protect against it -- how could you work
>> on string.py otherwise?
>>
>
> Emitting a warning message in such situations is being discussed in
> http://bugs.python.org/issue23809 though it is not a very lively
> discussion.

This is a separate issue of user code importing a user's own file 
instead of an stdlib file.


-- 
Terry Jan Reedy

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

Thread

Re: subprocess startup error Terry Reedy <tjreedy@udel.edu> - 2016-02-27 03:38 -0500

csiph-web