-
-
Notifications
You must be signed in to change notification settings - Fork 160
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
Comments
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. |
Use the existing `ctypes`-based Python bindings instead.
#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.
The text was updated successfully, but these errors were encountered: