> Any presence of a non-ascii character, even if it is in the
> comment only,
> would cause this problem. I have tried various encoding, with
> or without
> BOM, and also adding the encoding specification at the top of
> the file.
> All these give the same result. On the other hand a similar
> Java
> Hi Mark, thanks for the reply. The attribute you where
> thinking off is `Item`.
> What I'll need to work out now is which code page has been used to
> encode that Unicode string.
I'm not sure that is relevant. If I understand correctly, the code-page is
only used when converting from a string
P.S. The script can actually process unicode, passing unicode text to and
from other COM objects. E.g.
print u'\N{Euro Sign}'.encode('utf-8')
The only problem is the source code cannot have any non-ascii characters.
wy
> I find that putting any non-ascii character in the Python source co
I find that putting any non-ascii character in the Python source code
would cause an unspecific "Exception occurred" error. For example,
_u.py
# €
print 'hello'
g:\usr\bin\EmEditor Macros>cscript /e:python _u.py
Microsoft (R) Windows Script Host Version 5.6
Copyright (C) Microsoft Cor
On 7/1/06, Mark Hammond <[EMAIL PROTECTED]> wrote:
> > I thought I would be able to do
> >
> > my_string = unicode(Request("formstring"),"ISO-8859-1")> >
> > But i get:
> > coercing to Unicode: need string or buffer, instance found.
> > I'm guessing (and I mean guessing) this is because the CDispat
Hello,
I'm having an issue with Python/COM and Labview.
What I want to do is to instantiate Labview an let it open and execute a "VI"
(virtal instrument).
This works well in Visual Basic:
---
'Declare the object type of
On 30/06/2005 5:43 PM, Radovan Grznarik wrote:
> Hi,
>
> I am using EasyDialogs (AskFileForOpen) and I am not able to set the
> initial open path. I found in Python help that it should be 3rd
> parameter,
I doubt it. The Python *documentation*, whose first two lines ("2.7
EasyDialogs -- Basic Ma
