You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Not sure if it's a real issue or if I don't use it correctly, but I have two packages (namely pinocchio and curves) which call eigenpy::exposeQuaternion() in their c++ code for python API.
The issue is that the python Quaternion class only exist in the first package that I import, eg :
importpinocchioimportcurvespinocchio.Quaternion# okcurves.Quaternion# do not exist
importcurvesimportpinocchiopinocchio.Quaternion# do not existcurves.Quaternion# OK
Is there a way to correctly manage this or should I always keep care of the import order ? It could lead to hard to catch error for future users of both packages.
The text was updated successfully, but these errors were encountered:
Please see stack-of-tasks/pinocchio#817 for helps. It has solved the same issue than the one you had.
You then need to update pinocchio to get the latest release and the fix.
Not sure if it's a real issue or if I don't use it correctly, but I have two packages (namely pinocchio and curves) which call
eigenpy::exposeQuaternion()
in their c++ code for python API.The issue is that the python
Quaternion
class only exist in the first package that I import, eg :Is there a way to correctly manage this or should I always keep care of the import order ? It could lead to hard to catch error for future users of both packages.
The text was updated successfully, but these errors were encountered: