Daniel Oom

The release_interface call in `Ftdi.close()` may also raise an USBError. It prevents close() from cleaning up properly. Stack trace: ``` Traceback (most recent call last): File "./bin/ft232h-reconnect-test.py", line 21, in...

The test works on my machine: ``` > PYTHONPATH=. pyftdi/tests/ftdi.py s.Please disconnect FTDI device FTDI device may be gone: UsbError: [Errno 19] No such device (it may have been disconnected)...

I use the script in first post, you can also modify the test case like this: ``` diff --git a/pyftdi/tests/ftdi.py b/pyftdi/tests/ftdi.py index 096f113..bf4f880 100755 --- a/pyftdi/tests/ftdi.py +++ b/pyftdi/tests/ftdi.py @@ -137,7...

Weird I checked the docs for libusb_release_interface[1] and it states that the error LIBUSB_ERROR_NO_DEVICE can be returned which is what's happening for me. In the python usb library is turned...