Re: IDLE has suddenly become FAWLTY - so should I be hitting it with a big stick, or what?

On Tuesday, August 26, 2014 7:01:22 PM UTC-5, Steven D'Aprano wrote: > I think it is a serious design flaw that the standard > library and user code co-exist in a single namespace. I'm not sure if your wording is just clumsily and you meant: """ I think it is a serious design flaw that the

Re: IDLE has suddenly become FAWLTY - so should I be hitting it with a big stick, or what?

'python -m idlelib' gave me information about a file, ntpath.py, that I've edited before with notepad++. This file has been rewritten with a tab instead of 4 paces. The command suggested by Terry displayed an explicit message about wrong indentation. This error fixed, IDLE run again like a charm

Re: IDLE has suddenly become FAWLTY - so should I be hitting it with a big stick, or what?

In Command Prompt, 'python -m idlelib' helped me to dicover the problem source. An explicit message told that an indentation was insconsistant in the file ntpath.py I modified previously with notepad++. I replaced a tab by 4 spaces and IDLE run again like a charm. -- https://mail.python.org/m

Re: IDLE has suddenly become FAWLTY - so should I be hitting it with a big stick, or what?

On Tuesday, 26 August 2014 23:55:51 UTC+1, Twirlip2 wrote: > It doesn't seem immediately obvious how to get a definitive list > of which names to avoid using (and therefore, inadvertently > 'shadowing', as I did today). > > For example, >

Re: IDLE has suddenly become FAWLTY - so should I be hitting it with a big stick, or what?

On Wednesday, 27 August 2014 05:03:10 UTC+1, Terry Reedy wrote: > On 8/26/2014 9:11 PM, Twirlip2 wrote: > > > Firefox can't find the server at news.gmane.com. > > sorry. .org > > This is gmane.comp.python.general Found it now, thanks. I'll take my time and learn how to use it. I hope it's OK

Re: Python conquors the BBC [was Re: IDLE has suddenly become FAWLTY - so should I be hitting it with a big stick, or what?]

On Wednesday, 27 August 2014 09:12:07 UTC+1, Chris "Kwpolska" Warrick wrote: > On Wed, Aug 27, 2014 at 2:58 AM, Twirlip2 wrote: > > > > > I have plenty of ideas for improving the program, but first I have to > > re-organise the present spaghetti code in a more logical fashion. > > I have a bet

Re: Python conquors the BBC [was Re: IDLE has suddenly become FAWLTY - so should I be hitting it with a big stick, or what?]

On Wednesday, 27 August 2014 05:55:28 UTC+1, Chris Angelico wrote: > On Wed, Aug 27, 2014 at 1:13 PM, Rustom Mody wrote: > > On Wednesday, August 27, 2014 8:06:24 AM UTC+5:30, Chris Angelico wrote: > >> On Wed, Aug 27, 2014 at 10:58 AM, Twirlip2 wrote: > >> > > >> > So, please give me a few week

Re: Python conquors the BBC [was Re: IDLE has suddenly become FAWLTY - so should I be hitting it with a big stick, or what?]

On Wed, Aug 27, 2014 at 2:58 AM, Twirlip2 wrote: > It just pulls a lot of HTML and XML from the website, and extracts the > addresses of various other pages, and eventually *.WMA streams, and > hands the stream URLs over to XMPlay . > > It 'knows' what pages to visit, beca

Re: Python conquors the BBC [was Re: IDLE has suddenly become FAWLTY - so should I be hitting it with a big stick, or what?]

On Wed, Aug 27, 2014 at 1:13 PM, Rustom Mody wrote: > On Wednesday, August 27, 2014 8:06:24 AM UTC+5:30, Chris Angelico wrote: >> On Wed, Aug 27, 2014 at 10:58 AM, Twirlip2 wrote: >> > So, please give me a few weeks to improve my code, before posting it. (I >> > recently came across somewhere on

Re: IDLE has suddenly become FAWLTY - so should I be hitting it with a big stick, or what?

On 8/26/2014 9:11 PM, Twirlip2 wrote: On Wednesday, 27 August 2014 01:51:20 UTC+1, Terry Reedy wrote: On 8/26/2014 7:29 PM, Twirlip2 wrote: On Wednesday, 27 August 2014 00:20:56 UTC+1, Mark Lawrence wrote: Another lesson is that google grops is crap [...] You read my mind! (See parenthetica

Re: Python conquors the BBC [was Re: IDLE has suddenly become FAWLTY - so should I be hitting it with a big stick, or what?]

On Wednesday, August 27, 2014 8:06:24 AM UTC+5:30, Chris Angelico wrote: > On Wed, Aug 27, 2014 at 10:58 AM, Twirlip2 wrote: > > So, please give me a few weeks to improve my code, before posting it. (I > > recently came across somewhere on the Web where you can post code, but I > > forget where.)

Re: Python conquors the BBC [was Re: IDLE has suddenly become FAWLTY - so should I be hitting it with a big stick, or what?]

On Wed, Aug 27, 2014 at 10:58 AM, Twirlip2 wrote: > So, please give me a few weeks to improve my code, before posting it. (I > recently came across somewhere on the Web where you can post code, but I > forget where.) If you're looking for hosting, I recommend one of the source control hosting sit

Re: IDLE has suddenly become FAWLTY - so should I be hitting it with a big stick, or what?

On Wednesday, 27 August 2014 01:51:20 UTC+1, Terry Reedy wrote: > On 8/26/2014 7:29 PM, Twirlip2 wrote: > > On Wednesday, 27 August 2014 00:20:56 UTC+1, Mark Lawrence wrote: > >> Another lesson is that google grops is crap [...] > > You read my mind! (See parenthetical note at end of my most rece

Re: Python conquors the BBC [was Re: IDLE has suddenly become FAWLTY - so should I be hitting it with a big stick, or what?]

On Wednesday, 27 August 2014 01:58:16 UTC+1, Twirlip2 wrote: > It's a mess, but > it does at least keep local dependencies in a configuration file. (I > had no trouble getting it to run on two different PCs, under both XP > and Win98SE - and, if I recall correctly, also Vista, but I never use > t

Re: Python conquors the BBC [was Re: IDLE has suddenly become FAWLTY - so should I be hitting it with a big stick, or what?]

On Wednesday, 27 August 2014 01:21:32 UTC+1, Chris Angelico wrote: > On Wed, Aug 27, 2014 at 10:08 AM, Twirlip2 wrote: > > On Wednesday, 27 August 2014 01:04:18 UTC+1, Steven D'Aprano wrote: > >> Twirlip2 wrote: > >> > > >> > Since I require Python in order to listen to my beloved radio > >> > pr

Re: IDLE has suddenly become FAWLTY - so should I be hitting it with a big stick, or what?

On 8/26/2014 7:29 PM, Twirlip2 wrote: On Wednesday, 27 August 2014 00:20:56 UTC+1, Mark Lawrence wrote: Another lesson is that google grops is crap [...] You read my mind! (See parenthetical note at end of my most recent post.) You can access python-list (and a few thousand other tech list

Re: Python conquors the BBC [was Re: IDLE has suddenly become FAWLTY - so should I be hitting it with a big stick, or what?]

On Wed, Aug 27, 2014 at 10:08 AM, Twirlip2 wrote: > On Wednesday, 27 August 2014 01:04:18 UTC+1, Steven D'Aprano wrote: > >> Twirlip2 wrote: >> >> > Since I require Python in order to listen to my beloved radio programmes >> > reliably (don't get me started on the subject of the thrice-accursed B

Re: IDLE has suddenly become FAWLTY - so should I be hitting it with a big stick, or what?

On Wed, Aug 27, 2014 at 10:01 AM, Steven D'Aprano wrote: > Gregory Ewing wrote: > >> Although shadowing builtin module names is never a good >> idea, either! > > /s/builtin/standard library/ > > Quick! Name all the standard library modules, stat! > > In Python 3.3, there are something like 410 mod

Re: Python conquors the BBC [was Re: IDLE has suddenly become FAWLTY - so should I be hitting it with a big stick, or what?]

On Wednesday, 27 August 2014 01:04:18 UTC+1, Steven D'Aprano wrote: > Twirlip2 wrote: > > > Since I require Python in order to listen to my beloved radio programmes > > reliably (don't get me started on the subject of the thrice-accursed BBC > > website!), I therefore have IDLE running all the t

Re: IDLE has suddenly become FAWLTY - so should I be hitting it with a big stick, or what?

On Wednesday, 27 August 2014 01:01:22 UTC+1, Steven D'Aprano wrote: > Gregory Ewing wrote: > > > Although shadowing builtin module names is never a good > > idea, either! > > /s/builtin/standard library/ > > Quick! Name all the standard library modules, stat! > > In Python 3.3, there are some

Python conquors the BBC [was Re: IDLE has suddenly become FAWLTY - so should I be hitting it with a big stick, or what?]

Twirlip2 wrote: > Since I require Python in order to listen to my beloved radio programmes > reliably (don't get me started on the subject of the thrice-accursed BBC > website!), I therefore have IDLE running all the time, very probably > sometimes for weeks on end. Well, don't keep us in suspend

Re: IDLE has suddenly become FAWLTY - so should I be hitting it with a big stick, or what?

Gregory Ewing wrote: > Although shadowing builtin module names is never a good > idea, either! /s/builtin/standard library/ Quick! Name all the standard library modules, stat! In Python 3.3, there are something like 410 modules in the standard library. There's a reasonable chance that you've sh

Re: IDLE has suddenly become FAWLTY - so should I be hitting it with a big stick, or what?

On Wed, Aug 27, 2014 at 9:25 AM, Twirlip2 wrote: > I do really mean "continuously". I'm hopelessly addicted to listening to > repeats of classic comedy programmes on Radio 4 Extra; I often listen at > bedtime, and first thing in the morning; and I keep my computer running 24/7 > (shutting it do

Re: IDLE has suddenly become FAWLTY - so should I be hitting it with a big stick, or what?

On Wednesday, 27 August 2014 00:20:56 UTC+1, Mark Lawrence wrote: > Another lesson is that google grops is crap [...] You read my mind! (See parenthetical note at end of my most recent post.) I'm a recovered Usenet addict, of long standing. My excuse is that it was a near-emergency - I'd been

Re: IDLE has suddenly become FAWLTY - so should I be hitting it with a big stick, or what?

On Wednesday, 27 August 2014 00:07:03 UTC+1, Chris Angelico wrote: > On Wed, Aug 27, 2014 at 4:01 AM, Twirlip2 wrote: > > > I've been using IDLE with Python 3.4.0 on Windows XP (SP3), since March > > this year, and since May I've been running IDLE almost continuously, using > > it scores of t

Re: IDLE has suddenly become FAWLTY - so should I be hitting it with a big stick, or what?

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 simp

Re: IDLE has suddenly become FAWLTY - so should I be hitting it with a big stick, or what?

On Wed, Aug 27, 2014 at 4:01 AM, Twirlip2 wrote: > I've been using IDLE with Python 3.4.0 on Windows XP (SP3), since March this > year, and since May I've been running IDLE almost continuously, using it > scores of times every day, > Just to clarify: When you say "continuously", do you mean tha

Re: IDLE has suddenly become FAWLTY - so should I be hitting it with a big stick, or what?

On Tuesday, 26 August 2014 23:03:20 UTC+1, Gregory Ewing wrote: > Twirlip2 wrote: > > > There is probably some lesson I should learn from this. > > > > The lesson is probably that you shouldn't put the code > > you're developing somewhere that's on the default import path. Most of what I wa

Re: IDLE has suddenly become FAWLTY - so should I be hitting it with a big stick, or what?

Twirlip2 wrote: There is probably some lesson I should learn from this. The lesson is probably that you shouldn't put the code you're developing somewhere that's on the default import path. Although shadowing builtin module names is never a good idea, either! -- Greg -- https://mail.python.or

Re: IDLE has suddenly become FAWLTY - so should I be hitting it with a big stick, or what?

On 26/08/2014 20:58, Twirlip2 wrote: On Tuesday, 26 August 2014 20:44:35 UTC+1, Twirlip2 wrote: Meanwhile, let me try renaming my module, and see what happens ... Whoopee, IDLE is back! I need to sit down for a while, and just relax. Oh look, there's a nice comfy chair! Surely nothing un

Re: IDLE has suddenly become FAWLTY - so should I be hitting it with a big stick, or what?

On Tuesday, 26 August 2014 20:44:35 UTC+1, Twirlip2 wrote: > Meanwhile, let me try renaming my module, and see what happens ... Whoopee, IDLE is back! I need to sit down for a while, and just relax. Oh look, there's a nice comfy chair! Surely nothing unexpected can happen now. -- https://ma

Re: IDLE has suddenly become FAWLTY - so should I be hitting it with a big stick, or what?

On Tue, Aug 26, 2014 at 2:26 PM, Twirlip2 wrote: > On Tuesday, 26 August 2014 19:46:55 UTC+1, Terry Reedy wrote: >> On 8/26/2014 2:01 PM, Twirlip2 wrote: >> >> > [...] > > Here are the aforementioned error messages (sorry, I didn't realise I could > simply "select all" and "copy" text from a com

Re: IDLE has suddenly become FAWLTY - so should I be hitting it with a big stick, or what?

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,

Re: IDLE has suddenly become FAWLTY - so should I be hitting it with a big stick, or what?

On Tuesday, 26 August 2014 19:46:55 UTC+1, Terry Reedy wrote: > On 8/26/2014 2:01 PM, Twirlip2 wrote: > > > [...] Here are the aforementioned error messages (sorry, I didn't realise I could simply "select all" and "copy" text from a command window) - I hope the formatting doesn't get messed up

Re: IDLE has suddenly become FAWLTY - so should I be hitting it with a big stick, or what?

On Tuesday, 26 August 2014 19:46:55 UTC+1, Terry Reedy wrote: > On 8/26/2014 2:01 PM, Twirlip2 wrote: > > > I've been using IDLE with Python 3.4.0 on Windows XP (SP3), > > ... > > > > Does all non-Python stuff seem to be working? Yes. > > For a few days, I'd been frequently running a secon

Re: IDLE has suddenly become FAWLTY - so should I be hitting it with a big stick, or what?

On 2014-08-26, Twirlip2 wrote: Careful. If you hit it with a big stick it might fall on your head and give you a concussion making it hard to remember to not mention the war. -- Grant Edwards grant.b.edwardsYow! I hope the at

Re: IDLE has suddenly become FAWLTY - so should I be hitting it with a big stick, or what?

On 8/26/2014 2:01 PM, Twirlip2 wrote: I've been using IDLE with Python 3.4.0 on Windows XP (SP3), ... Does all non-Python stuff seem to be working? For a few days, I'd been frequently running a second instance of IDLE, to test a new version of the same script. Today, having closed this insta

IDLE has suddenly become FAWLTY - so should I be hitting it with a big stick, or what?

I've been using IDLE with Python 3.4.0 on Windows XP (SP3), since March this year, and since May I've been running IDLE almost continuously, using it scores of times every day, mostly to run the same script (for running a media player on BBC WMA streams, to bypass the dreaded iPlayer). No probl