Kudos

[zacharyyamaoka]

This is great package! Thanks Andrej.

I really like how you interact with moveit via the moveit_node vs another api as with the offical moveit python api

I was wondering what your plans are for future with the offical moveit python api now being avaliable though...

[AndrejOrsula]

Hello,

I was wondering what your plans are for future with the offical moveit python api now being avaliable though...

For now, I will continue to review & merge PRs and answer issues. However, I do not actively use pymoveit2 anymore, so I won't actively develop new features or make any extensive modifications myself. It is used in some projects, so maintaining backwards-compatibility in a single branch for multiple distributions would be ideal.

I still haven't tried the official MoveIt 2 Python bindings because I work on other things, but it is what I generally recommend people try first if they can.

[zacharyyamaoka]

Thanks for this clarity!!

…

On Sun, Apr 28, 2024 at 3:44 AM Andrej Orsula ***@***.***> wrote: Hello, I was wondering what your plans are for future with the offical moveit python api now being avaliable though... For now, I will continue to review & merge PRs and answer issues. However, I do not actively use pymoveit2 anymore, so I won't actively develop new features or make any extensive modifications myself. It is used in some projects, so maintaining backwards-compatibility in a single branch for multiple distributions would be ideal. I still haven't tried the official MoveIt 2 Python bindings because I work on other things, but it is what I generally recommend people try first if they can. — Reply to this email directly, view it on GitHub <#64 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/AGZUQL66XXUW6DWIBNPLG3TY7THI3AVCNFSM6AAAAABG4UXIA2VHI2DSMVQWIX3LMV43SRDJONRXK43TNFXW4Q3PNVWWK3TUHM4TENJRGU2TE> . You are receiving this because you authored the thread.Message ID: ***@***.***>