cython-hidapi #62
Labels
No labels
3rdparty
Android
API
Author does not respond
bsd
bug
build system/CI
ci-virtual-device
CMake
Contributions Welcome
Core
dependencies
device-specific
documentation
don't_merge
duplicate
enhancement
Example
Haiku
hidraw
hotplug
info required
invalid
libusb
macOS
Misc
Not an issue
question
Release
Test
Test GUI
Windows
wontfix
No milestone
No assignees
1 participant
Notifications
Due date
No due date set.
Dependencies
No dependencies set
Reference
gh-libusb/hidapi#62
Loading…
Reference in a new issue
No description provided.
Delete branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Hi!
I am the current maintainer of cython-hidapi - a python binding for hidapi. I see you've resurrected the hidapi project and I'd like to ask you whether you would like to take part in maintainership of cython-hidapi package as well (i.e. move the package under your libusb organization where we'd maintain the package together).
Maybe we can even move the bindings into the main hidapi repo, because the cython-hidapi uses hidapi repo as its submodule, so it makes a lot of sense.
Hi @prusnak!
I am a fan of keeping the repositories separate, simply because it makes it easier to manage, with only one language's quirks and build process needing to be dealt with. Especially here because of the many languages wrap
hidapi.There's also a discussion as to which Python
hidapilibrary to support. I like howcython-hidapibuilds for all OSes and includes pre-built binaries of its library with a statically-builthidapion PyPi. I feel this preferable than relying on a "system" install ofhidapi(I think whatpyhidapidoes)Agree with @todbot, better keep it separate
there is also similar discussion at https://github.com/apmorton/pyhidapi/pull/29 with same conclusion
in any case, it is great to know, that there is another project, that has switched to this repository
Agree with @todbot and @Youw.
Thank you for good work being done @prusnak!