libusb
Python binding for the libusb C library.
Overview
libusb-1.0 API Reference on Documentation.
libusb uses the underlying libusb C shared library as specified in libusb.cfg (included libusb-X.X.* is the default), but there is also ability to specify it programmatically by one of the following ways:
import libusb
libusb.config(LIBUSB="libusb C shared library absolute path")
# or
libusb.config(LIBUSB=None) # included libusb-X.X.* will be usedAbout original libusb:
Borrowed from the original website:
Overview
libusb is a C library that provides generic access to USB devices. It is intended to be used by developers to facilitate the production of applications that communicate with USB hardware.
It is portable: Using a single cross-platform API, it provides access to USB devices on Linux, macOS, Windows, etc.
It is user-mode: No special privilege or elevation is required for the application to communicate with a device.
It is version-agnostic: All versions of the USB protocol, from 1.0 to 3.1 (latest), are supported.
What platforms are supported?
Linux, macOS, Windows (Vista or newer), Android, OpenBSD/NetBSD, Haiku, Solaris.
For additional information, please consult the FAQ or the Wiki.
Requirements
- It is a fully independent package.All necessary things are installed during the normal installation process.
ATTENTION: currently fully tested only for Windows.
Installation
Prerequisites:
Python 3.11 or higher
with C libusb 1.0.30 is a primary test environment.
pip
To install run:
python -m pip install --upgrade libusb
Development
Prerequisites:
Development is strictly based on nox. To install it run:
python -m pip install --upgrade nox
Visit Development page.
Installation from sources:
clone the sources:
git clone https://github.com/karpierz/libusb libusb
and run:
python -m pip install ./libusb
or on development mode:
python -m pip install --editable ./libusb
License
Copyright (c) 2016-2026 Adam KarpierzLicensed under the zlib/libpng LicensePlease refer to the accompanying LICENSE file.
Sponsoring
1 maintainer
Metadata
1 maintainer
Release files for libusb 1.0.30.post2
For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.
Source distribution (sdist)
| File | Size | Uploaded | Provenance | Actions |
|---|---|---|---|---|
| libusb-1.0.30.post2.tar.gz | 964.1 kB | Without provenance | Details for libusb-1.0.30.post2.tar.gz |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Actions Reset |
|---|---|---|---|---|
| libusb-1.0.30.post2-py3-none-any.whl | Python 3 | none | any | Details for libusb-1.0.30.post2-py3-none-any.whl |
Total release size: 1.9 MB
Release files / libusb-1.0.30.post2.tar.gz
| Download URL | libusb-1.0.30.post2.tar.gz |
|---|---|
| Size | 964.1 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
e40fb66d14becbca71f7b93e9324c8922d4ab2174073b478f86cf1b9eb4c05f4
|
|
BLAKE2b-256 checksum How to use checksums |
b220b12ef2c8d2455cc09576faf41c4300b21fa55ed010b5f210ad035c547067
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/7.0.0 CPython/3.14.8
|
Release files / libusb-1.0.30.post2-py3-none-any.whl
| Download URL | libusb-1.0.30.post2-py3-none-any.whl |
|---|---|
| Size | 925.8 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
479a796a6bc52b1c8e4bf03c70a043f60063501b0a9d8c24ac310b7beafc2b7c
|
|
BLAKE2b-256 checksum How to use checksums |
feb0778c036595889968c9f6c8fcf04067000a6aba0787603751ad75d618c6d2
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/7.0.0 CPython/3.14.8
|
Security for libusb 1.0.30.post2
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
No provenance found
None of the files in this release were uploaded with provenance metadata.
A note on package security
PyPI is a repository for distributing packages, not a service for auditing them. While third-party security researchers and our staff do their best to detect and remove malicious packages, PyPI cannot guarantee the quality, security or suitability of any given package.
To learn more about protecting yourself from malicious actors, visit our package security documentation.
