GH-44614: [Python][C++] Add version suffix to libarrow_python* libraries

[raulcd]

Rationale for this change

We are currently not setting library version suffixes for arrow python C++ libraries but we do so for libarrow C++.

What changes are included in this PR?

Add the same logic that we use for libarrow.

Are these changes tested?

I've validated manually that the suffixes are generated.

tree | grep libarrow_python
│       │   ├── libarrow_python.so -> libarrow_python.so.1900
│       │   ├── libarrow_python.so.1900 -> libarrow_python.so.1900.0.0
│       │   ├── libarrow_python.so.1900.0.0
│   │   ├── libarrow_python.pxd
│   ├── libarrow_python.so -> libarrow_python.so.1900
│   ├── libarrow_python.so.1900 -> libarrow_python.so.1900.0.0
│   ├── libarrow_python.so.1900.0.0

Are there any user-facing changes?

We will generate so libraries with version suffixes.

• GitHub Issue: [Python] Add version suffix to libarrow_python* libraries #44614

[raulcd]

@github-actions crossbow submit -g python

[github-actions]

⚠️ GitHub issue #44614 has been automatically assigned in GitHub to PR creator.

[raulcd]

@github-actions crossbow submit -g wheel

[github-actions]

Revision: 07b1f4e

Submitted crossbow builds: ursacomputing/crossbow @ actions-a85f386da9

Task	Status
example-python-minimal-build-fedora-conda
example-python-minimal-build-ubuntu-venv
test-conda-python-3.10
test-conda-python-3.10-cython2
test-conda-python-3.10-hdfs-2.9.2
test-conda-python-3.10-hdfs-3.2.1
test-conda-python-3.10-pandas-latest-numpy-latest
test-conda-python-3.10-substrait
test-conda-python-3.11
test-conda-python-3.11-dask-latest
test-conda-python-3.11-dask-upstream_devel
test-conda-python-3.11-hypothesis
test-conda-python-3.11-pandas-latest-numpy-1.26
test-conda-python-3.11-pandas-latest-numpy-latest
test-conda-python-3.11-pandas-nightly-numpy-nightly
test-conda-python-3.11-pandas-upstream_devel-numpy-nightly
test-conda-python-3.11-spark-master
test-conda-python-3.12
test-conda-python-3.12-cpython-debug
test-conda-python-3.13
test-conda-python-3.9
test-conda-python-3.9-pandas-1.1.3-numpy-1.19.5
test-conda-python-emscripten
test-cuda-python-ubuntu-22.04-cuda-11.7.1
test-debian-12-python-3-amd64
test-debian-12-python-3-i386
test-fedora-39-python-3
test-ubuntu-22.04-python-3
test-ubuntu-22.04-python-313-freethreading
test-ubuntu-24.04-python-3

[github-actions]

Revision: 07b1f4e

Submitted crossbow builds: ursacomputing/crossbow @ actions-c44ab3558a

Task	Status
python-sdist
wheel-macos-monterey-cp310-cp310-amd64
wheel-macos-monterey-cp310-cp310-arm64
wheel-macos-monterey-cp311-cp311-amd64
wheel-macos-monterey-cp311-cp311-arm64
wheel-macos-monterey-cp312-cp312-amd64
wheel-macos-monterey-cp312-cp312-arm64
wheel-macos-monterey-cp313-cp313-amd64
wheel-macos-monterey-cp313-cp313-arm64
wheel-macos-monterey-cp313-cp313t-amd64
wheel-macos-monterey-cp313-cp313t-arm64
wheel-macos-monterey-cp39-cp39-amd64
wheel-macos-monterey-cp39-cp39-arm64
wheel-manylinux-2-28-cp310-cp310-amd64
wheel-manylinux-2-28-cp310-cp310-arm64
wheel-manylinux-2-28-cp311-cp311-amd64
wheel-manylinux-2-28-cp311-cp311-arm64
wheel-manylinux-2-28-cp312-cp312-amd64
wheel-manylinux-2-28-cp312-cp312-arm64
wheel-manylinux-2-28-cp313-cp313-amd64
wheel-manylinux-2-28-cp313-cp313-arm64
wheel-manylinux-2-28-cp313-cp313t-amd64
wheel-manylinux-2-28-cp313-cp313t-arm64
wheel-manylinux-2-28-cp39-cp39-amd64
wheel-manylinux-2-28-cp39-cp39-arm64
wheel-manylinux-2014-cp310-cp310-amd64
wheel-manylinux-2014-cp310-cp310-arm64
wheel-manylinux-2014-cp311-cp311-amd64
wheel-manylinux-2014-cp311-cp311-arm64
wheel-manylinux-2014-cp312-cp312-amd64
wheel-manylinux-2014-cp312-cp312-arm64
wheel-manylinux-2014-cp313-cp313-amd64
wheel-manylinux-2014-cp313-cp313-arm64
wheel-manylinux-2014-cp313-cp313t-amd64
wheel-manylinux-2014-cp313-cp313t-arm64
wheel-manylinux-2014-cp39-cp39-amd64
wheel-manylinux-2014-cp39-cp39-arm64
wheel-windows-cp310-amd64
wheel-windows-cp311-amd64
wheel-windows-cp312-amd64
wheel-windows-cp313-amd64
wheel-windows-cp39-amd64

[raulcd]

CI failures are currently occurring at nightly jobs.
Example files for one of the generated wheels:

-- Installing: /arrow/python/build/lib.linux-x86_64-cpython-312/pyarrow/./libarrow_python.so.1900.0.0
-- Installing: /arrow/python/build/lib.linux-x86_64-cpython-312/pyarrow/./libarrow_python.so.1900
-- Installing: /arrow/python/build/lib.linux-x86_64-cpython-312/pyarrow/./libarrow_python.so
-- Installing: /arrow/python/build/lib.linux-x86_64-cpython-312/pyarrow/./libarrow_python_parquet_encryption.so.1900.0.0
-- Installing: /arrow/python/build/lib.linux-x86_64-cpython-312/pyarrow/./libarrow_python_parquet_encryption.so.1900
-- Installing: /arrow/python/build/lib.linux-x86_64-cpython-312/pyarrow/./libarrow_python_parquet_encryption.so
-- Installing: /arrow/python/build/lib.linux-x86_64-cpython-312/pyarrow/./libarrow_python_flight.so.1900.0.0
-- Installing: /arrow/python/build/lib.linux-x86_64-cpython-312/pyarrow/./libarrow_python_flight.so.1900
-- Installing: /arrow/python/build/lib.linux-x86_64-cpython-312/pyarrow/./libarrow_python_flight.so

[assignUser]

LGTM

[eltoder]

@raulcd thank you!

[conbench-apache-arrow]

After merging your PR, Conbench analyzed the 3 benchmarking runs that have been run so far on merge-commit d7641dc.

There were no benchmark performance regressions. 🎉

The full Conbench report has more details. It also includes information about 1 possible false positive for unstable benchmarks that are known to sometimes produce them.