Vincent Pelletier

@ynsta : [python-libusb1](https://github.com/vpelletier/python-libusb1) developer here. I just pushed a [more advanced example](https://github.com/vpelletier/python-libusb1/blob/master/examples/hotplug_advanced.py) on how one may write a hotplug driver, which may help with this bug and with #15 ....

> it did not work out-of-the-box with retroarch My apologies. It looks like I had a non-default setting (maybe I started retroarch long ago and forgot ?). Using X as...

It is very unfortunate that libusb chose to add a variadic in their API, as these are basically impossible to wrap with ctypes (I was trying to find a positive...

> Just wondering if it is possible to split the python binding into different functions. This is definitely possible, but I can understand libusb maintainers not wanting to multiply such...

> I believe the failure concern may be resolvable for the current implementations, if the maximum number of parameters is always passed. Extra ones will simply be ignored, and I...

> - as the name mangling differs between calling conventions, ctypes is able to infer the calling convention to use for every library symbol (at least those loaded by name)....

So, my current understanding is that `libusb_set_option` may work as long as: - easy/seems unlikely to be an issue: - I explicitly load it as cdecl on Windows (which will...

You're welcome. There is no hurry, on my side it's also getting pretty busy, and will probably remain so for about a month.

Hello, This means `frame.f_back` is None (frame is topmost), but call stack is not empty (so there is a known caller). The error traceback is consistent with no caller existing...

I am interested in taking these here, yes. I am not sure whether I would prefer separate `.pyi` files or comment-style annotations though: I would tend to prefer the type...