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


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

Re: subprocess startup error

Started byTerry Reedy <tjreedy@udel.edu>
First post2016-02-27 03:38 -0500
Last post2016-02-27 03:38 -0500
Articles 1 — 1 participant

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: subprocess startup error Terry Reedy <tjreedy@udel.edu> - 2016-02-27 03:38 -0500

#103563 — Re: subprocess startup error

FromTerry Reedy <tjreedy@udel.edu>
Date2016-02-27 03:38 -0500
SubjectRe: subprocess startup error
Message-ID<mailman.166.1456562333.20994.python-list@python.org>
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

[toc] | [standalone]


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


csiph-web