× pip subprocess to install build dependencies did not run successfully.
│ exit code: 1
╰─> [12 lines of output]
Collecting setuptools
Using cached setuptools-75.2.0-py3-none-any.whl.metadata (6.9 kB)
Collecting wheel
Using cached wheel-0.44.0-py3-none-any.whl.metadata (2.3 kB)
Collecting packaging
Using cached packaging-24.1-py3-none-any.whl.metadata (3.2 kB)
Collecting cython<=3.0.0,>=0.29.1
Using cached Cython-3.0.0-py2.py3-none-any.whl.metadata (3.1 kB)
Collecting kivy_deps.gstreamer_dev~=0.3.3
Using cached kivy_deps.gstreamer_dev-0.3.4-cp313-cp313-win_amd64.whl.metadata (247 bytes)
ERROR: Could not find a version that satisfies the requirement kivy_deps.sdl2_dev~=0.7.0 (from versions: 0.8.0)
ERROR: No matching distribution found for kivy_deps.sdl2_dev~=0.7.0
[end of output]
note: This error originates from a subprocess, and is likely not a problem with pip.
error: subprocess-exited-with-error
× pip subprocess to install build dependencies did not run successfully.
│ exit code: 1
╰─> See above for output.
note: This error originates from a subprocess, and is likely not a problem with pip.
@2AD this is an excellent point. If you’re going to reach out for help, its probably better to fault towards over sharing details. That said, providing the full command line is par for the course.
… however, all the information needed is present as it turns out.
@MRAB is correct but the might qualifiers are not needed.
From the OP output:
Using cached kivy_deps.gstreamer_dev-0.3.4-cp313-cp313-win_amd64.whl.metadata (247 bytes)
That shows the Python in question is in fact 3.13.
The error then:
ERROR: Could not find a version that satisfies the requirement kivy_deps.sdl2_dev~=0.7.0 (from versions: 0.8.0)
Looking at kivy_deps.sdl2_dev 0.8.0, there is a published wheel for Python 3.13: kivy-deps.sdl2-dev · PyPI, but 0.8.0 is not compatible with the ~=0.7.0 specifier (it’s equivalent to >=0.7,<0.8).
Looking at kivy_deps.sdl2_dev 0.7.0, which would be compatible with the ~=0.7.0 specifier, there is no Python 3.13 wheel, and there is no sdist to be able to build one with either: kivy-deps.sdl2-dev · PyPI
And so you are exactly in the situation @MRAB suggested, for certain.
The Python packaging situation is not awesome and you will need to learn to read these tea leaves going forward to stay sane. Hopefully these details help you fish. For a more normal distribution, you could attempt using a VCS requirement on kivy_deps.sdl2_dev but it seems like the kivy folks have a fairly opaque build process for these kivy-deps.* wheels. You’ll probably just need to search their issues / file one if not already flagged.