subprocess startup error

Terry Reedy tjreedy at
Sat Feb 27 03:38:27 EST 2016

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__ at> wrote:
>>>> Shweta Dinnimani wrote:
>>>>> i saved my file as since than i'm facing this error
>>>> Rename that file to something that does not clash with the module
>>>> names in
>>>> the standard library, 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 otherwise?
> Emitting a warning message in such situations is being discussed in
> 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

More information about the Python-list mailing list