Feature request: USBContext.handleEventsCompleted() about python-libusb1 HOT 3 OPEN

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."

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 handleEvents in a loop, and, instead of calling an event handler function in the code waiting for a specific transfer to complete, wait on a mutex
which would get set in the completion callback ?

from python-libusb1.

That would be pretty cool, especially if it could provide some sort of "wait for this list of USBTransfers to complete" functionality

from python-libusb1.

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.

from python-libusb1.