I have thus far been working with python 2.7, for no particular reason aside
from that it's been stable/comfortable/usable from when I really got going with
python, but, while think latest release version of python is something like
3.4, what are the reasons, if any, for sticking to/with the
On 5/11/2014 2:39 PM, Jacob Kruger wrote:
I have thus far been working with python 2.7, for no particular reason aside
from that it's been stable/comfortable/usable from when I really got going
with python, but, while think latest release version of python is something
like 3.4, what are the
Thanks.
And, yes, know it wasn't specifically python-win32 specific smile, but, in
terms of platform compatibility, my primary issue thus far has been generating
windows executables while making use of various external modules, and one of
the new releases along the lines of this is a newer
Hi £ukasz,
when you use a COM-Interface via VB for example things like
foo.bar(0) = foo
are possible (as I just read these are properties).
In Python this syntax is not working. Instead, getters and setters are
generated by PyWin.
I guess somewhere (probably in the files generated by
On 11/05/2014 21:39, Jacob Kruger wrote:
I have thus far been working with python 2.7, for no particular reason
aside from that it's been stable/comfortable/usable from when I really
got going with python, but, while think latest release version of python
is something like 3.4, what are the
On 9/05/2014 1:14 AM, Red Gator wrote:
Sure I can do that. But after this debacle I find I need to know why.
* Why does my object come up as win32com.gen_py.None.Map when it
should come up as 'win32com.gen_py.fiddly-GUID-bits.Map or even
