You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Wheels for Python 3.14 are currently missing on PyPI.
I think it would also help to include a source distribution (sdist), since pip can automatically build a wheel from the sdist when a prebuilt one isn’t available.
Just got bit by this today.
silently failing isn't really an optimal outcome.
For anyone stuck in the interim I added a script to pull dlls from an old version that at least in my specific use case seemed to fix it. Note this is a bad solution for temporary use only.
@Pog3k@icc-jand Since libusb_package seems to be abandonware, I have made and published a new version at libusb_package_tng, which can also be installed via pip. This new version works with Python 3.14 and doesn't require rebuilds every time the Python version goes up (which seems a bit ridiculous since the only time you should need to rebuild anything is if libusb releases a new version that you want to upgrade to).
Apologies to the maintainers if this is an inappropriate place to post this.
thanks, what are the plans for the future as I have a PR ready to switch to the TNG package....
will you publish publish a --pre release for 3.15 in preparation for a quick update once it is released ?
@Josverl, we'll publish a release shortly which enables Python 3.14 and most likely will work also with 3.15. If there will be additional changes required for 3.15 we address them after 3.15 is the out of pre-release.
release shortly which enables Python 3.14 and most likely will work also with 3.15.
OK, I'll wait for that to decide what path to take.
For me the value of a pre-release would be to allow validating and finding and fixing eventual issues in advance. Rather than skewing a month for every tiered dependency. Normally I could do that by installing from main/master, but I don't think that works in this case.
Still, better a bit late than never. So thanks for the efforts.
Activity
feat: Add warning for missing libusb backend on Windows+Latest Python
icc-jand commentedon Apr 9, 2026
Just got bit by this today.
silently failing isn't really an optimal outcome.
For anyone stuck in the interim I added a script to pull dlls from an old version that at least in my specific use case seemed to fix it. Note this is a bad solution for temporary use only.
fix_libusb_py314.zip
feat: Add warning for missing libusb backend on Windows+Latest Python
feat: Add warning for missing libusb backend on Windows+Latest Python
tgree commentedon May 19, 2026
@Pog3k @icc-jand Since libusb_package seems to be abandonware, I have made and published a new version at libusb_package_tng, which can also be installed via pip. This new version works with Python 3.14 and doesn't require rebuilds every time the Python version goes up (which seems a bit ridiculous since the only time you should need to rebuild anything is if libusb releases a new version that you want to upgrade to).
Apologies to the maintainers if this is an inappropriate place to post this.
feat: Add warning for missing libusb backend on Windows+Latest Python
RobertRostohar commentedon Jun 19, 2026
Should be addressed with #32.
dogtopus commentedon Jun 19, 2026
@RobertRostohar Nice. Would you please also bump the libusb version to 1.0.30?
Josverl commentedon Jun 19, 2026
thanks, what are the plans for the future as I have a PR ready to switch to the TNG package....
will you publish publish a --pre release for 3.15 in preparation for a quick update once it is released ?
RobertRostohar commentedon Jun 19, 2026
@dogtopus, updating to the latest libusb requires more efforts. Please open a separate issue for that.
RobertRostohar commentedon Jun 19, 2026
@Josverl, we'll publish a release shortly which enables Python 3.14 and most likely will work also with 3.15. If there will be additional changes required for 3.15 we address them after 3.15 is the out of pre-release.
Josverl commentedon Jun 19, 2026
OK, I'll wait for that to decide what path to take.
For me the value of a pre-release would be to allow validating and finding and fixing eventual issues in advance. Rather than skewing a month for every tiered dependency. Normally I could do that by installing from main/master, but I don't think that works in this case.
Still, better a bit late than never. So thanks for the efforts.
RobertRostohar commentedon Jun 19, 2026
Can you try out the latest released v1.0.26.4 with Python 3.15? I believe it should work already.
dogtopus commentedon Jun 19, 2026
There was already #22 so it makes sense to continue the discussion there.
Josverl commentedon Jun 20, 2026
I can confirm Version: 1.0.26.4 works for my application on :
Using uv's python-build-standalone .
Ill continue testing and update here.
feat: Add warning for missing libusb backend on Windows+Latest Python
RobertRostohar commentedon Jun 23, 2026
Updating to latest libusb is covered by #35.