Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Two Python APIs #338

Closed
nitsch opened this issue Dec 15, 2017 · 1 comment · Fixed by #459
Closed

Two Python APIs #338

nitsch opened this issue Dec 15, 2017 · 1 comment · Fixed by #459

Comments

@nitsch
Copy link
Collaborator

nitsch commented Dec 15, 2017

#335 (comment) mentions ctypes-based Python bindings, and indeed, some scripts in examples/python/ use this new API.

What are the plans for the Python bindings? Is the new API supposed to eventually replace the SWIG-based one? Having two different APIs for the same thing is likely to generate some confusion.

@thp
Copy link
Owner

thp commented Dec 16, 2017

Yes, it's expected that the new bindings in https://github.com/thp/psmoveapi/blob/master/bindings/python/psmoveapi.py are the ones that should be used for future projects. The new bindings mirror the new C/C++-based API in https://github.com/thp/psmoveapi/blob/master/include/psmoveapi.h -- however, not all low-level functions are mapped by this API yet (and might not ever be), so that's why the old ones will probably still hang around a little longer.

thp added a commit that referenced this issue Dec 20, 2022
Use the existing `ctypes`-based Python bindings instead.
@thp thp linked a pull request Dec 20, 2022 that will close this issue
@thp thp closed this as completed in #459 Dec 23, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants