Ob.constraints['b:c'] vs ob.blenderObject.pose.bones['b'].constraints['c']

Game Engine Game Engine Support and Discussion
1

hello there,
I like long titles.

I was used to:

c = sc.objects[‘my_armature’].constraints[‘bonename:constname’]
c.enforce = …

to play with rig constraints.

but it looks like it’s not the way anymore: arm.constraints list seems always empty in upbge0361 when I try to poll it. arm.update, animation playing etc… always an empty list, and no
'bonename:constraintname" resolution/

it looks like we should use the bpy now, it seems, with :

c = sc.objects[armname].blenderObject.pose.bones[bonename].constraints[constname]

(I got this elegant line from here)

since the old way is still in the upBGE API documentation:

https://upbge.org/docs/latest/api/bge.types.BL_ArmatureObject.html#bge.types.BL_ArmatureObject

https://upbge.org/docs/latest/api/bge.types.BL_ArmatureConstraint.html#bge.types.BL_ArmatureConstraint

I was wondering if the existing BGE ArmatureObject class will be fixed or dropped, or as a rwrite as a “proxy” class ?