[Python-modules-team] Bug#854426: python3-usb: Device.attach_kernel_driver should probably the release interfaces first

[Celelibi]

Package: python3-usb
Version: 1.0.0-1
Severity: minor

Dear Maintainer,

When trying to end properly a program, I try to reattach the kernel
driver to the device. However, this fails if one interface is still
claimed by the program.

Sice pyusb take care of claiming the interfaces, it should probably also
take care of releasing them. Otherwise, calling
device.attach_kernel_device always fail with a "busy" error.

Best regards,
Celelibi

-- System Information:
Debian Release: 9.0
  APT prefers testing
  APT policy: (990, 'testing'), (500, 'unstable')
Architecture: amd64 (x86_64)

Kernel: Linux 4.9.0-1-amd64 (SMP w/8 CPU cores)
Locale: LANG=fr_FR.UTF-8, LC_CTYPE=fr_FR.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)

Versions of packages python3-usb depends on:
ii  libusb-1.0-0  2:1.0.21-1
pn  python3:any   <none>

python3-usb recommends no packages.

python3-usb suggests no packages.

-- no debconf information