Path: csiph.com!v102.xanadu-bbs.net!xanadu-bbs.net!goblin1!goblin2!goblin.stu.neva.ru!newsfeed1.swip.net!uio.no!news.tele.dk!news.tele.dk!small.news.tele.dk!newsgate.cistron.nl!newsgate.news.xs4all.nl!post.news.xs4all.nl!not-for-mail Return-Path: X-Original-To: python-list@python.org Delivered-To: python-list@mail.python.org X-Spam-Status: OK 0.002 X-Spam-Evidence: '*H*': 1.00; '*S*': 0.00; 'from:addr:yahoo.co.uk': 0.04; 'subject:IDLE': 0.04; 'broke': 0.09; 'lawrence': 0.09; 'received:80.91': 0.09; 'received:80.91.229': 0.09; 'received:gmane.org': 0.09; 'received:list': 0.09; 'python': 0.11; 'language.': 0.14; 'effect,': 0.16; 'meanwhile,': 0.16; 'naming': 0.16; 'received:80.91.229.3': 0.16; 'received:plane.gmane.org': 0.16; 'renaming': 0.16; 'spacing': 0.16; 'subject: \n ': 0.16; 'prevent': 0.16; 'all.': 0.16; 'language': 0.16; 'wrote:': 0.18; 'module': 0.19; 'trying': 0.19; 'thanks.': 0.20; 'creating': 0.23; 'header:User-Agent:1': 0.23; 'certainly': 0.24; 'module,': 0.24; 'url:moin': 0.24; 'looks': 0.24; 'source': 0.25; 'least': 0.26; 'header:X-Complaints-To:1': 0.27; 'header:In-Reply-To:1': 0.27; 'thus': 0.29; "i'm": 0.30; 'url:mailman': 0.30; 'code': 0.31; 'url:wiki': 0.31; 'subject:what': 0.31; 'this.': 0.32; 'probably': 0.32; 'another': 0.32; 'url:python': 0.33; 'subject:with': 0.35; 'something': 0.35; 'but': 0.35; 'google': 0.35; 'there': 0.35; 'done': 0.36; 'url:listinfo': 0.36; 'subject:?': 0.36; 'url:org': 0.36; 'should': 0.36; 'list': 0.37; 'to:addr:python-list': 0.38; 'files': 0.38; 'anything': 0.39; 'sure': 0.39; 'to:addr:python.org': 0.39; 'received:org': 0.40; 'url:mail': 0.40; 'even': 0.60; 'read': 0.60; 'above,': 0.60; 'temporarily': 0.60; 'august': 0.61; 'simple': 0.61; 'name': 0.63; 'skip:n 10': 0.64; 'our': 0.64; 'charset:windows-1252': 0.65; 'it!': 0.67; 'truth': 0.81; '"big': 0.84 X-Injected-Via-Gmane: http://gmane.org/ To: python-list@python.org From: Mark Lawrence Subject: Re: IDLE has suddenly become FAWLTY - so should I be hitting it with a big stick, or what? Date: Wed, 27 Aug 2014 00:20:56 +0100 References: <4eec9365-4103-4474-a47f-ea665b265b1e@googlegroups.com> <5a9b5715-382b-4a6b-be90-c535ad14740a@googlegroups.com> Mime-Version: 1.0 Content-Type: text/plain; charset=windows-1252; format=flowed Content-Transfer-Encoding: 7bit X-Gmane-NNTP-Posting-Host: host-78-147-188-27.as13285.net User-Agent: Mozilla/5.0 (Windows NT 6.3; WOW64; rv:31.0) Gecko/20100101 Thunderbird/31.0 In-Reply-To: X-BeenThere: python-list@python.org X-Mailman-Version: 2.1.15 Precedence: list List-Id: General discussion list for the Python programming language List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Newsgroups: comp.lang.python Message-ID: Lines: 33 NNTP-Posting-Host: 2001:888:2000:d::a6 X-Trace: 1409095270 news.xs4all.nl 2857 [2001:888:2000:d::a6]:41555 X-Complaints-To: abuse@xs4all.nl Xref: csiph.com comp.lang.python:77080 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