Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]
Groups > comp.lang.python > #103545
| From | Emile van Sebille <emile@fenx.com> |
|---|---|
| Newsgroups | comp.lang.python |
| Subject | Re: subprocess startup error |
| Date | 2016-02-26 06:57 -0800 |
| Message-ID | <mailman.155.1456498685.20994.python-list@python.org> (permalink) |
| References | <CAFW38mFPYdee0dvmF5655FffxqGT7rpmYU1yMegGf1RSe8a7rg@mail.gmail.com> <CAFW38mHJDNsD48zbiyo3pXMpJJhPSjPvvwCij0-VjozDSuFscw@mail.gmail.com> <napk16$oi5$1@ger.gmane.org> <CAHVvXxRwmaejwnLMXZ-YTqVC=d7PAKABpxrTA3gY9tKmB-dE9Q@mail.gmail.com> |
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? Emile
Back to comp.lang.python | Previous | Next | Find similar | Unroll thread
Re: subprocess startup error Emile van Sebille <emile@fenx.com> - 2016-02-26 06:57 -0800
csiph-web