MINOR: [Integration][CI] Remove Python pinning in integration build

[pitrou]

Rationale for this change

Pythonnet now seems to be compatible with Python versions up to 3.15:
https://github.com/pythonnet/pythonnet/blob/d2d27164cdcb62ea022a51ffc3ed78f338f01803/.github/workflows/main.yml#L49

Are these changes tested?

Yes, by corresponding CI job.

Are there any user-facing changes?

No.

[pitrou]

@github-actions crossbow submit conda ubuntuverify*

[github-actions]

Unable to match any tasks for `*ubuntu*verify*`
The Archery job run can be found at: https://github.com/apache/arrow/actions/runs/33399675668

[pitrou]

@github-actions crossbow submit conda verifyubuntu*

[kou]

https://github.com/apache/arrow/actions/runs/33406037337/job/99533744366?pr=51099#step:13:346

  #9 26.27   python-3.11.16-h8ab3286_0_cpython    102MB

Hmm. Python 3.11 was still used.

[pitrou]

Yes, weirdly. The constraint solver may be doing a suboptimal choice.

[pitrou]

Ping @raulcd

[raulcd]

the ci/docker/conda-integration.dockerfile uses ci/docker/conda-cpp.dockerfile as base and there we define Python 3.11, see:

arrow/ci/docker/conda-cpp.dockerfile

Line 26 in 397b3d0

ARG python=3.11

We could bump the base one or override and install a newer one on the conda-integration.dockerfile file.

[pitrou]

@raulcd Oh, you're right. I think we can bump this version.

[pitrou]

@github-actions crossbow submit conda

[github-actions]

Revision: 16d7028

Submitted crossbow builds: ursacomputing/crossbow @ actions-d78c302548

Task	Status
example-python-minimal-build-fedora-conda
test-conda-cpp
test-conda-cpp-valgrind
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-hdfs-2.9.2
test-conda-python-3.11-hdfs-3.2.1
test-conda-python-3.11-hypothesis
test-conda-python-3.11-pandas-2.2.2-numpy-2.0.2
test-conda-python-3.11-spark-master
test-conda-python-3.12
test-conda-python-3.12-pandas-latest-numpy-latest
test-conda-python-3.13
test-conda-python-3.13-pandas-latest-numpy-2.1.3
test-conda-python-3.13-pandas-latest-numpy-latest
test-conda-python-3.14
test-conda-python-3.14-cpython-debug
test-conda-python-3.14-pandas-nightly-numpy-nightly
test-conda-python-3.14-pandas-upstream_devel-numpy-nightly
test-conda-python-emscripten
verify-rc-source-cpp-linux-conda-latest-amd64
verify-rc-source-cpp-macos-conda-amd64
verify-rc-source-integration-linux-conda-latest-amd64
verify-rc-source-integration-macos-conda-amd64
verify-rc-source-python-linux-conda-latest-amd64
verify-rc-source-python-macos-conda-amd64
verify-rc-source-ruby-linux-conda-latest-amd64

[raulcd]

Seems to use 3.14 now: https://github.com/apache/arrow/actions/runs/34210589556/job/102010384170?pr=51099

  #9 25.09   Package folder                       Size
  #9 25.09 ─────────────────────────────────────────────
  #9 25.09   /opt/conda/pkgs
  #9 25.09 ─────────────────────────────────────────────
  #9 25.09 
  #9 25.09   libffi-3.7.0-h81df57d_1             271kB
  #9 25.09   nodejs-24.19.0-h50021de_1            76MB
  #9 25.09   python-3.14.7-hcd007b5_106_cp314     94MB

[pitrou]

I'll merge then.

Side question: there are many places where an old Python version is hard-coded as default, for example:

arrow/ci/docker/conda-python-dask.dockerfile

Line 21 in f14ae5b

ARG python=3.11

I don't think it matters because usually those would be overriden through compose.yaml and the PYTHON environment variable, but do we want to bump them anyway?

[raulcd]

I don't think it matters because usually those would be overriden through compose.yaml and the PYTHON environment variable, but do we want to bump them anyway?

I usually bump all those when an old Python version is EOL'd. I am fine with both bumping them or just keep testing with the oldest Python supported.