On 26/02/2016 15:08, 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 <__pete...@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.
Thanks for the link. I knew that I remembered a discussion about this
but frustratingly couldn't find it for myself :(
--
My fellow Pythonistas, ask not what our language can do for you, ask
what you can do for our language.
Mark Lawrence
--
https://mail.python.org/mailman/listinfo/python-list
