I'm converting working Perl COM scripts to Python (ActivePython
2.5.1.1)and I've hit an odd situation where win32com throws a 'Type
mismatch' error on a string.
It's odd because a) it works in ActiveState Perl, b) other methods in
the object work just fine in Python, and c) it looks suspiciously l
Reedick, Andrew wrote:
> It's odd because a) it works in ActiveState Perl, b) other methods in
> the object work just fine in Python, and c) it looks suspiciously like a
> key collision in an internal hash.
>
No, I think the debug log disproves this. The second call does not find
its attribute
Mark suggested that I get some feedback from the community regarding
some of the issues involved in creating a Unicode build of win32api.
Some functions already allow you to call the ansi or wide-character version,
such as FormatMessage/FormatMessageW. This leaves some ambiguity
as to how they sh
Roger Upole wrote:
> Mark suggested that I get some feedback from the community regarding
> some of the issues involved in creating a Unicode build of win32api.
>
> Some functions already allow you to call the ansi or wide-character version,
> such as FormatMessage/FormatMessageW. This leaves some
Tim Roberts wrote:
> Roger Upole wrote:
>> Mark suggested that I get some feedback from the community regarding
>> some of the issues involved in creating a Unicode build of win32api.
>>
>> Some functions already allow you to call the ansi or wide-character
>> version,
>> such as FormatMessage/For
