[Python SDK] Create `sync-python-version.sh` to keep python versions in sync across folders and docker images

[slbotbm]

Description

Create a bash script similar to sync-rust-version.sh that runs in CI and pre-commit hooks and checks that the python versions being used are all in sync. Currently we use Python 3.10.

Component

Python SDK

Proposed solution

No response

Alternatives considered

No response

[hubcio]

Keep in mind that for wheels we build for many python versions. See .github/workflows/_build_python_wheels.yml - I think that this script should also check whether selected python version is present in versions that we build for wheels.

[Phanindra899]

Hi @hubcio ,
I’d like to work on this.
My plan is to add a bash script (similar to sync-rust-version.sh) that:
• Extracts the primary Python version (currently 3.10) from the appropriate config location
• Verifies that the same version is used consistently across CI workflows and pre-commit configuration
• Ensures the selected version is included in the wheel build matrix (_build_python_wheels.yml)
• Fails with a clear error message if any mismatch is detected
This script can then be wired into CI and pre-commit to prevent version drift.
Please let me know if this approach aligns with your expectations, and I can proceed.

[Agentx402]

Great issue! This is a solid initiative to maintain consistency across the Python SDK components.

I'd suggest checking out the existing sync-rust-version.sh script as a template—it'll give you a good starting point for the structure and approach. You might also want to identify all locations where Python versions are currently specified (Dockerfiles, pyproject.toml, CI configs, etc.) to ensure the script covers everything. Looking forward to seeing this improvement!

[Agentx402]

Great issue! This is a solid DevOps/CI improvement that will help prevent subtle bugs caused by Python version mismatches across the project. Since there's already a sync-rust-version.sh to use as a reference template, you're in a great position — I'd suggest closely mirroring its structure and checking places like Dockerfiles, pyproject.toml, .python-version files, and any CI workflow YAML files for Python version references. Good luck, and thanks for helping keep the Apache Iggy Python SDK consistent! 🎉

[Phanindra899]

Hi, thanks for the guidance! I’ll work on this by following the structure of sync-rust-version.sh and create a similar sync-python-version.sh to keep Python version references consistent across Dockerfiles, pyproject.toml, and CI workflows. I’ll use a single source of truth and make sure everything stays aligned.
I’ll open a PR once it’s ready.