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
It looks like there are no prebuilt wheels for Python 3.13 on PyPI yet, so it will not work out of the box on Python 3.13. However, the library seems to work fine on Python 3.13 from my quick test.
You can build it from source or install using this test wheel file artifact from this Github action.
I'll try to release a new version soon, which will have prebuilt wheels for Python 3.13. As @PimDoos discovered, the CI is already in place, I just need to find the time for the actual release process.
My project Chordamap is stuck on Python 3.12 as well because of the dependency on this library. I would greatly appreciate a new release so I can update my project to the latest Python version.
Reacted by Joséphine Wolf Oberholtzer, Karmak23 and quagly
I'm trying to build fresh on Windows to code a new midi project, with latest python 3.14, following the RTD page, and it fails for another reason:
(build env : VSC++ latest as of today, python 3.14 from installer, powershell up-to-date, PATH updated, python-rtmidi cloned from github repo)
python -m pip build
[...]
Has header "semaphore.h" : YES
Program python3 found: YES (C:\Users\olive\AppData\Local\Temp\build-env-h8xm5__j\Scripts\python.exe)
Has header "Python.h" : YES
..\src\meson.build:3:17: ERROR: File rtmidi/RtMidi.cpp does not exist.
A full log can be found at C:\Users\olive\AppData\Local\Temp\build-via-sdist-fd__60z3\python_rtmidi-1.6.0\.mesonpy-73o4b70x\meson-logs\meson-log.txt
ERROR Backend subprocess exited when trying to invoke build_wheel
Needless to say the "full log" is unavailable because the build env is auto-cleaned against my will before I can open it in explorer.
I've cloned the rtmidi source code from github (version 6.0.0) in python-rtmidi/src/rtmidi/ which was empty, but it fails with exactly the same error. It seems it create a temp build env and doesn't pick the rtmidi source up. Where should I put it, or how to specify where the C++ code is for the build process to find it ?
While we wait for a new PyPI release here, I cut my own nanobind-based binding for RtMidi and published wheels for Linux/OSX/Windows Python 3.10 through 3.14: https://github.com/supriya-project/supriya-midi. I tried to keep the interface very similar to this library's API.
Reacted by tieu-sys, professor-hippo, quagly and Kris Holdich
Hi @SpotlightKid, thanks for all your work on python-rtmidi. I maintain IMPSY, a Python system for AI musical instruments that uses python-rtmidi through mido. At the moment IMPSY users on Python 3.13 need a compiler (and ALSA headers on a Raspberry Pi) to install it, and I'm looking at moving to 3.14 soon.
I noticed that master already has the 1.6.0 changes and working wheel builds, but the cibuildwheel setup stops at 3.13. I've made a small PR that adds 3.14 wheels and updates cibuildwheel (#229). The wheel builds and tests pass on my fork for Linux, macOS and Windows.
If it helps, I'm happy to test a release candidate or help with anything else that would get 1.6.0 out. Thanks again!
Activity
PimDoos commentedon Apr 15, 2025
It looks like there are no prebuilt wheels for Python 3.13 on PyPI yet, so it will not work out of the box on Python 3.13. However, the library seems to work fine on Python 3.13 from my quick test.
You can build it from source or install using this test wheel file artifact from this Github action.
tieu-sys commentedon Apr 16, 2025
Thanks, I tried the wheel and it works perfectly for my usage.
Thanks !
I hope it will be available soon on PyPI.
Have a good day !
SpotlightKid commentedon Apr 16, 2025
I'll try to release a new version soon, which will have prebuilt wheels for Python 3.13. As @PimDoos discovered, the CI is already in place, I just need to find the time for the actual release process.
ohcibi commentedon Aug 14, 2025
Building the package on macos with apple silicon fails.
This is the error:
SpotlightKid commentedon Aug 18, 2025
Probably the Cython-generated C source needs to be re-generated.
I still need to release a new version with official Python 3.13 support. I will try to do so towards the end of the month.
In the meantime, you can try to build from the HEAD of the git repo, e.g. with:
Maboroshy commentedon Sep 19, 2025
Any updates on this? My project - MIDI Scripter depends on python-rtmidi and is currently uninstallable from pip for 3.13.
Bubobubobubobubo commentedon Oct 19, 2025
Hello. Any update on this? I am also trying to upgrade my application from Python 3.12 to Python 3.13.
Require Python >= 3.12
josephine-wolf-oberholtzer commentedon Feb 11, 2026
I was able to get past the OSX 3.13
use of undeclared identifier 'sem_timedwait'build failure with this patch:Would still love a release! My work is stuck on Python 3.12.
archth commentedon Feb 14, 2026
My project Chordamap is stuck on Python 3.12 as well because of the dependency on this library. I would greatly appreciate a new release so I can update my project to the latest Python version.
Karmak23 commentedon Feb 17, 2026
I'm trying to build fresh on Windows to code a new midi project, with latest python 3.14, following the RTD page, and it fails for another reason:
(build env : VSC++ latest as of today, python 3.14 from installer, powershell up-to-date, PATH updated, python-rtmidi cloned from github repo)
Needless to say the "full log" is unavailable because the build env is auto-cleaned against my will before I can open it in explorer.
I've cloned the rtmidi source code from github (version 6.0.0) in
python-rtmidi/src/rtmidi/which was empty, but it fails with exactly the same error. It seems it create a temp build env and doesn't pick the rtmidi source up. Where should I put it, or how to specify where the C++ code is for the build process to find it ?I see the thing seem to compile file on some linux hosts (eg. https://packages.msys2.org/packages/mingw-w64-x86_64-rtmidi). Do I really need to get a linux machine to be able to python+midi ?
josephine-wolf-oberholtzer commentedon Feb 17, 2026
@Karmak23 If you clone this repo recursively, the
rtmidisubmodule will get cloned too. It already includes theRtMidi.cppfile.Czaki commentedon Apr 10, 2026
@SpotlightKid Any chance on a next release?
josephine-wolf-oberholtzer commentedon Apr 19, 2026
While we wait for a new PyPI release here, I cut my own nanobind-based binding for RtMidi and published wheels for Linux/OSX/Windows Python 3.10 through 3.14: https://github.com/supriya-project/supriya-midi. I tried to keep the interface very similar to this library's API.
tieu-sys commentedon May 18, 2026
I did a pull request here to provide the 3.13 whee (#226)
Before pypi release, you can try the wheel with these artefacts: (https://github.com/tieu-sys/python-rtmidi/actions/runs/25916616387#artifacts)
cpmpercussion commentedon Sep 26, 2026
Hi @SpotlightKid, thanks for all your work on python-rtmidi. I maintain IMPSY, a Python system for AI musical instruments that uses python-rtmidi through mido. At the moment IMPSY users on Python 3.13 need a compiler (and ALSA headers on a Raspberry Pi) to install it, and I'm looking at moving to 3.14 soon.
I noticed that master already has the 1.6.0 changes and working wheel builds, but the cibuildwheel setup stops at 3.13. I've made a small PR that adds 3.14 wheels and updates cibuildwheel (#229). The wheel builds and tests pass on my fork for Linux, macOS and Windows.
If it helps, I'm happy to test a release candidate or help with anything else that would get 1.6.0 out. Thanks again!