UsbDK support about python-libusb1 HOT 3 OPEN

In the temporary "next" branch, I pushed a few weeks back several libusb features that I was not wrapping yet. One of which is libusb_init_context, exposed as new arguments to USBContext.__init__, especially use_usbdk which takes a boolean (false by default). libusb_init_context allows side-stepping the libusb_set_option variadic topic.

Could you try that branch and report whether it works, and how usable it looks to you ?

One caveat: as this is not released yet, I consider I am still allowed to change the newly introduced API. Basically, the argument name could change or it could have to be provided in another way. But I think I am happy enough with the current implementation.

And on another level: I am currently very busy on a personal level, so I have basically no time to work on the next release. Things should hopefully calm down in the next few months, freeing some time.

from python-libusb1.

In the temporary "next" branch, I pushed a few weeks back several libusb features that I was not wrapping yet. One of which is libusb_init_context, exposed as new arguments to USBContext.__init__, especially use_usbdk which takes a boolean (false by default). libusb_init_context allows side-stepping the libusb_set_option variadic topic.

Could you try that branch and report whether it works, and how usable it looks to you ?

One caveat: as this is not released yet, I consider I am still allowed to change the newly introduced API. Basically, the argument name could change or it could have to be provided in another way. But I think I am happy enough with the current implementation.

And on another level: I am currently very busy on a personal level, so I have basically no time to work on the nex

Sure, don't worry about being busy or anything else and focus on whatever you need to. It's also perfectly fine if it changes. I'll let you know how it goes after trying it.

from python-libusb1.

In the temporary "next" branch, I pushed a few weeks back several libusb features that I was not wrapping yet. One of which is libusb_init_context, exposed as new arguments to USBContext.__init__, especially use_usbdk which takes a boolean (false by default). libusb_init_context allows side-stepping the libusb_set_option variadic topic.

Could you try that branch and report whether it works, and how usable it looks to you ?

One caveat: as this is not released yet, I consider I am still allowed to change the newly introduced API. Basically, the argument name could change or it could have to be provided in another way. But I think I am happy enough with the current implementation.

And on another level: I am currently very busy on a personal level, so I have basically no time to work on the next release. Things should hopefully calm down in the next few months, freeing some time.

Apologies for the late reply:
It doesn't seem to work as now what happens is

libusb: error [windows_set_option] UsbDk backend not available
# error traceback
  result = self.getByVendorIDAndProductID(
    self.open()
mayRaiseUSBError(libusb1.libusb_init_context(
raise __STATUS_TO_EXCEPTION_DICT.get(value, __USBError)(value)
LIBUSB_ERROR_NOT_FOUND [-5]

from python-libusb1.