Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]
Groups > comp.lang.python > #103547 > unrolled thread
| Started by | Wolfgang Maier <wolfgang.maier@biologie.uni-freiburg.de> |
|---|---|
| First post | 2016-02-26 16:08 +0100 |
| Last post | 2016-02-26 16:08 +0100 |
| 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 Wolfgang Maier <wolfgang.maier@biologie.uni-freiburg.de> - 2016-02-26 16:08 +0100
| From | Wolfgang Maier <wolfgang.maier@biologie.uni-freiburg.de> |
|---|---|
| Date | 2016-02-26 16:08 +0100 |
| Subject | Re: subprocess startup error |
| Message-ID | <mailman.156.1456499311.20994.python-list@python.org> |
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.
Back to top | Article view | comp.lang.python
csiph-web