Re: Cannot understand error message

2008-02-14 Thread Bruno Desthuilliers
Bill Davy a écrit : > "Bruno Desthuilliers" <[EMAIL PROTECTED]> > wrote in message news:[EMAIL PROTECTED] (snip) >>> Many thanks for the help. Must get a bigger screen and new eyes. >> Or a better code editor. > > I just grabbed what was on the shelf. Is there a Python plug-in for MSVC? > ;-)

Re: Cannot understand error message

2008-02-14 Thread Bill Davy
"Bruno Desthuilliers" <[EMAIL PROTECTED]> wrote in message news:[EMAIL PROTECTED] > Bill Davy a écrit : > (snip) >> Doh. > > (snip) > >> Interesting that some colourers work better than others. It must be >> quite a challenge. >> >> IDLE did not offer a full traceback just a pop-up. > > Mmm... T

Re: Cannot understand error message

2008-02-14 Thread Bruno Desthuilliers
Dennis Lee Bieber a écrit : > On Wed, 13 Feb 2008 17:29:59 -, "Bill Davy" <[EMAIL PROTECTED]> > declaimed the following in comp.lang.python: > >> The colouring in IDLE does not indicate a bad string. >> > I don't use IDLE, but PythonWin's editor identified it quite easily > after I paste

Re: Cannot understand error message

2008-02-14 Thread Bruno Desthuilliers
Bill Davy a écrit : (snip) > Doh. (snip) > Interesting that some colourers work better than others. It must be quite a > challenge. > > IDLE did not offer a full traceback just a pop-up. Mmm... That sure is bad. Isn't there an option to get a better behaviour? Anyway, just trying to run you

Re: Cannot understand error message

2008-02-14 Thread Bill Davy
"Chris" <[EMAIL PROTECTED]> wrote in message news:[EMAIL PROTECTED] > It doesn't like all that text in the previous one... > > Just before s = '' you have 4 double quotes to close to doc-string > instead of 3. Doh. I had put in the s = '' to see if I could force IDLE to say something more, and

Re: Cannot understand error message

2008-02-14 Thread Bruno Desthuilliers
Steven D'Aprano a écrit : > On Wed, 13 Feb 2008 17:29:59 +, Bill Davy wrote: > >> The following code produces an error message (using Idle with Py 2.4 and >> 2.5). "There's an error in your program: EOL while scanning >> single-quoted string". It comes just after "s = ''" (put there to try >

Re: Cannot understand error message

2008-02-13 Thread Chris
On Feb 14, 2:25 am, Steven D'Aprano <[EMAIL PROTECTED] cybersource.com.au> wrote: > On Wed, 13 Feb 2008 17:29:59 +, Bill Davy wrote: > > The following code produces an error message (using Idle with Py 2.4 and > > 2.5). "There's an error in your program: EOL while scanning > > single-quoted st

Re: Cannot understand error message

2008-02-13 Thread Steven D'Aprano
On Wed, 13 Feb 2008 17:29:59 +, Bill Davy wrote: > The following code produces an error message (using Idle with Py 2.4 and > 2.5). "There's an error in your program: EOL while scanning > single-quoted string". It comes just after "s = ''" (put there to try > and isolate the broken string).

Re: Cannot understand error message

2008-02-13 Thread Chris
It doesn't like all that text in the previous one... Just before s = '' you have 4 double quotes to close to doc-string instead of 3. -- http://mail.python.org/mailman/listinfo/python-list

Re: Cannot understand error message

2008-02-13 Thread Chris
On Feb 13, 7:29 pm, "Bill Davy" <[EMAIL PROTECTED]> wrote: > The following code produces an error message (using Idle with Py 2.4 and > 2.5). "There's an error in your program: EOL while scanning single-quoted > string". It comes just after "s = ''" (put there to try and isolate the > broken stri

Cannot understand error message

2008-02-13 Thread Bill Davy
The following code produces an error message (using Idle with Py 2.4 and 2.5). "There's an error in your program: EOL while scanning single-quoted string". It comes just after "s = ''" (put there to try and isolate the broken string). It would be good if the error message pointed me to the st