Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]
Groups > comp.lang.python > #103545 > unrolled thread
| Started by | Emile van Sebille <emile@fenx.com> |
|---|---|
| First post | 2016-02-26 06:57 -0800 |
| Last post | 2016-02-26 06:57 -0800 |
| 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.
Re: subprocess startup error Emile van Sebille <emile@fenx.com> - 2016-02-26 06:57 -0800
| From | Emile van Sebille <emile@fenx.com> |
|---|---|
| Date | 2016-02-26 06:57 -0800 |
| Subject | Re: subprocess startup error |
| Message-ID | <mailman.155.1456498685.20994.python-list@python.org> |
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 top | Article view | comp.lang.python
csiph-web