-
Notifications
You must be signed in to change notification settings - Fork 67
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
Feature request: USBContext.handleEventsCompleted() #94
Comments
This would be "Multi-threaded applications and asynchronous I/O", and especially the "libusb_handle_events() from multiple threads" section. Would it make sense to have a USB event handling thread which would just call |
That would be pretty cool, especially if it could provide some sort of "wait for this list of USBTransfers to complete" functionality |
Sorry, I was unclear: what I was suggesting is something which can be done outsite of python-libusb1, in your implementation of the transfer callback. I would rather keep as much of threading, locking and global tracking outside of python-libusb1 as possible. |
It seems like, looking at the libusb async API docs, this function is the best way to solve the problem of "handle events only until a specific transfer is done." However, it doesn't currently exist in python-libusb1 and is marked as TODO. I'd love it if you could add this function, especially if it could get a Python wrapper that allows waiting for a list of transfers to complete.
The text was updated successfully, but these errors were encountered: