Hi GStreamer Community,
I have noticed some inconsistency regarding the Python versions targeted by the Windows MSVC binaries. Specifically, in the 1.26.x release, the binaries included _gi.cp313-win_amd64.pyd (targeting Python 3.13), but the recent 1.28 release appears to include _gi.cp39-win_amd64.pyd (targeting Python 3.9).
This inconsistency makes it difficult to maintain stable deployment environments. I have two questions for the maintainers and the community:
-
Versioning Strategy: Is there a specific reason the Python target version fluctuates between releases? Is there a plan to standardize on a specific Python “Long Term Support” version or provide multiple
.pydfiles for common Python versions (e.g., 3.10, 3.12, 3.13) in the official installer? -
Custom Compilation: Since the pre-built binaries often don’t match our local environment, what is the current recommended workflow for compiling only the Python bindings (
gst-pythonandgobject-introspection) on Windows to match a specific Python version?
I would appreciate any guidance on the Meson flags or environment setup required to build these bindings against a local Python installation while linking them to the official GStreamer MSVC library binaries.
Best regards