Fredrik Lundh wrote:
> Steve Holden wrote:
>
>
>>Can I ask if you are specifying a source encoding in your file with a
>>pragma (?) like
>>
>># -*- coding: iso-8859-15 -*-
>>
>>I've noticed what appear to be spurious syntax errors from time to time
>>on such files, and have been attempting to deb
Fredrik Lundh wrote:
> Steve Holden wrote:
>
>
>>Can I ask if you are specifying a source encoding in your file with a
>>pragma (?) like
>>
>># -*- coding: iso-8859-15 -*-
>>
>>I've noticed what appear to be spurious syntax errors from time to time
>>on such files, and have been attempting to deb
"Robin Becker" <[EMAIL PROTECTED]> wrote in message
news:[EMAIL PROTECTED]
> This behaviour doesn't occur with 2.4.2 or 2.4 only with 2.4.1. I looked for
> some bug fix in the recently released 2.4.2 that related, but couldn't find
> anything obvious.
One of the various codecs fixes, I think. Bu
Steve Holden wrote:
> Can I ask if you are specifying a source encoding in your file with a
> pragma (?) like
>
> # -*- coding: iso-8859-15 -*-
>
> I've noticed what appear to be spurious syntax errors from time to time
> on such files, and have been attempting to debug the problem for some
> time
Robin Becker wrote:
> Whilst testing the excellent xlrd http://www.python.org/pypi/xlrd/0.3a1
> I came across the following strangeness when trying to add an import of os to
> assist with debugging/tracing.
>
>
> At line 66 I replaced
>
> import sys
>
> with import sys, os
>
> and then ran py
Whilst testing the excellent xlrd http://www.python.org/pypi/xlrd/0.3a1
I came across the following strangeness when trying to add an import of os to
assist with debugging/tracing.
At line 66 I replaced
import sys
with import sys, os
and then ran python runxlrd.py --help and got this error wh
