It appears that the cause of this problem was indirect.
I input something incorrect as an argument to an xplane sdk function
and the cos/integer type error followed.
Thanks for the help. The diagnostic functions I learned in this thread
will be very helpful in the future.
moonman wrote:
>
I'm using ActiveState PythonV2.4.1
I'm certainly not affecting 'math'. I wonder if the XPlane SDK Python
binding is touching anything.
I'll download the latest ActiveState Python and keep on plugging.
Thanks!
Mikael Olofsson wrote:
> moonman wrote:
> >
something about 'math'. Does it really expect an
int?
Moonman
Larry Bates wrote:
> First: Always post cut-paste tracebacks so we can see actual
> error message.
>
> Second: print out self.ACphi, XPLMGetDataf(self.ACphi) and
> math.radians(XPLMGetDataf(self.ACphi)) before
.
Is there something that I'm completely missing about how Python does
tyonig or something?
Thanks in advance,
Moonman
--
http://mail.python.org/mailman/listinfo/python-list
