On 26/08/2014 20:44, Twirlip2 wrote:
On Tuesday, 26 August 2014 20:20:22 UTC+1, Twirlip2 wrote:
Mercifully, it looks like Python is not broken, but I have done something Silly!
[...]
What I don't yet understand is why Python is trying to execute anything at all.
But I'm sure there's a simple explanation, and there'll certainly be at least a
workaround, even if I have to temporarily move all my recently-edited source
code files to another location!
The truth is that Python WAS broken, but it was (unsurprisingly) me wot broke
it!
I had, in effect, already hit it with a "big stick", by naming one of my
newly-created modules 'code.py' - thus evidently creating a name conflict with the
standard module I:\Python34\Lib\code.py.
There is probably some lesson I should learn from this.
Meanwhile, let me try renaming my module, and see what happens ...
Another lesson is that google grops is crap, so would you please access
this list via https://mail.python.org/mailman/listinfo/python-list or
read and action this https://wiki.python.org/moin/GoogleGroupsPython to
prevent us seeing the double line spacing and single line paragraphs
above, thanks.
--
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
