Generally, there are four possible causes for this problem:

1. You didn't install libusb library.
2. Your libusb library isn't in the standard shared library paths.
3. Your libusb version is too old.
4. Your PyUSB version is too old.

To debug what's wrong, run the following script in your environment:

import os
os.environ['PYUSB_DEBUG'] = 'debug'
import usb.core
usb.core.find()

This will print debug messages to the console. If you still have problems to figure out what's going on, please ask for help in the mailing list, providing the debug output.

On Windows, pyocd/libusb-package is a convenient [1] [2] way to provide the necessary libusb 1.0 DLL, as well as a suitable PyUSB backend and a easy to use wrapper over PyUSB's find() API:

# with pure PyUSB
for dev in usb.core.find(find_all=True):
    print(dev)

# with pyocd/libusb-package
for dev in libusb_package.find(find_all=True):
    print(dev)

Alternatively, the libusb 1.0 DLL can be manually copied from an official release archive into the C:\Windows\System32 system folder, or packaged together with the complete application.

Occasionally, on Windows: check out the documentation of the backend in use (either libusb 1.0 or libusb 0.1/libusb-win32).

Here is an example for the libusb1 backend:

>>> import usb.core
>>> from usb.backend import libusb1
>>> be = libusb1.get_backend()
>>> dev = usb.core.find(backend=be)

Check the Specify libraries by hand section in the tutorial.

Linux and BSD are typically set up in a way in which root permissions are needed for low level/generic access to USB devices.

Using sudo or similar tools is one way to temporarily give a program access to USB devices, but there are several reasons why that may not be ideal in all situations.

A better way on Linux is to use udev rules to allow unprivileged access to specific USB devices by certain users:

# these examples assume a hypothetical device with 1111:aaaa vendor:product IDs

# allow r/w access by all local/physical sessions (seats)
# https://github.com/systemd/systemd/issues/4288
SUBSYSTEMS=="usb", ATTRS{idVendor}=="1111", ATTRS{idProduct}=="aaaa", TAG+="uaccess"

# allow r/w access by users of the plugdev group
SUBSYSTEMS=="usb", ATTRS{idVendor}=="1111", ATTRS{idProduct}=="aaaa", GROUP="plugdev", MODE="0660"

# allow r/w access by all users
SUBSYSTEMS=="usb", ATTRS{idVendor}=="1111", ATTRS{idProduct}=="aaaa", MODE="0660"

Typically set_configuration() is called during device initialization. The libusb documentation on libusb_set_configuration() states:

If you call this function on a device already configured with the selected configuration, then this function will act as a lightweight device reset: it will issue a SET_CONFIGURATION request using the current configuration, causing most USB-related device state to be reset (altsetting reset to zero, endpoint halts cleared, toggles reset).

Calling write() subsequently will therefore result in a timeout error.

One solution to this behaviour is to consider the currently active configuration, as described in the configuration selection and handling. "If the configuration we want is already active, then we don't have to select any configuration":

try:
    cfg = dev.get_active_configuration()
except usb.core.USBError:
    cfg = None
if cfg is None or cfg.bConfigurationValue != cfg_desired:
    dev.set_configuration(cfg_desired)