When I print the dir(motionactuator) I get a list that includes setDRot rather than the setdRot, that is in my pdf manual. I also get an error that says setDRot requires four arguments, rather than the one argument(a list of three numbers) that my pdf says the setdrot takes. Are ther any changes I’m unaware of?
Is this and old bug? Have I finally lost it, from trying to make an axil rotate to the slope of the ground for the past three days?(possibly 
) ,waz up wit dis?
what version of blender is this from?
in 2.28 a lot of python has changed, and will probably not be going back, for example
Window.DrawProgressbar()
is now
Window.draw_ProgressBar()
(grr)
but it looks like you have figured out what you need to do
I’ve come across several places where the documentation is wrong.
For example, the documentation says applyImpulse() takes one 3 element python list. In truth though, it takes 2 lists of 3 elements each. (I spent a lot of time with that one, trying to figure out what was going wrong…)
chrisjengle: Yours is another case of incorrect documentation, the correct spelling is setDRot() not setdRot(). The 4 arguments it takes are the amount of rotation for x, y, z, and the switch for local movement.
z3r0 d: since setDRot() applies to motion actuators, he’s probably not using anything above 2.25 
Ok, cool. thanks! but what do you mean by a switch? like TRUE and FALSE? and true means it’s a local rotation, and false means global?
(and this is a little off subject, but how do you trigger an actuator to fire only once in python? do you just use a sensor that is set to fire once, and then use addActive Actuator to make the actuator go once each time the script is triggered?)
By “switch” I mean boolean, it can be either zero (false) or not-zero (true). Yes, in this case true will cause local rotation, false will be global.
In the python docs you can read what values are considered true or false by python. Here’s a link directly to the appropriate page:
http://www.python.org/doc/current/lib/truth.html