I have the same problems and googled a lot but just found Sunny Carter's
requests with no solution. Is there any, yet?
Thanks!
___
python-win32 mailing list
python-win32@python.org
http://mail.python.org/mailman/listinfo/python-win32
: Mark Hammond [mailto:skippy.hamm...@gmail.com]
Sent: 05 January 2010 07:58
To: Sunny Carter
Cc: python-win32@python.org
Subject: Re: [python-win32] Boolean type changed in Python 3.0?
On 5/01/2010 3:51 AM, Sunny Carter wrote:
Hi all,
I'm trying my posting again with a different subject so
On 27/01/2010 8:21 AM, Sunny Carter wrote:
Mark - just wondered if you had any update on this?
I believe Roger checked a fix in for this over the last few days. I'm
not sure when a new binary build will be available though, but probably
not within a few weeks...
Cheers,
Mark
Fabulous - thanks for the update.
Sunny
-Original Message-
From: Mark Hammond [mailto:skippy.hamm...@gmail.com]
Sent: 27 January 2010 17:28
To: Sunny Carter
Cc: python-win32@python.org
Subject: Re: [python-win32] Boolean type changed in Python 3.0?
On 27/01/2010 8:21 AM, Sunny Carter
From looking at the source of
PyCom_VariantFromPyObject in oleargs.cpp,
the check for a boolean is done after the check for
an int. PyLong_Check is used to determine
if the object should be converted to one of the variant
integer types. Apparently in Python 3.x, this now returns
True for a
Hi all,
I'm trying my posting again with a different subject so that it is more generic.
I am having problems calling across the win32 API using a Boolean argument in
Python 3.0 (False in my python script) which is not recognised as a Boolean
(The error I get back from setattr is 'Boolean
On 5/01/2010 3:51 AM, Sunny Carter wrote:
Hi all,
I'm trying my posting again with a different subject so that it is more
generic.
I am having problems calling across the win32 API using a Boolean
argument in Python 3.0 (False in my python script) which is not
recognised as a Boolean (The error