0389ee789a
Python 3.14 has to wait: the Windows build needs pywinpty, which is held at 2.0.x for andfoy/pywinpty#545, and 2.0.x cannot be built for 3.14. Note that beside both pins.
39 lines
2.0 KiB
Plaintext
39 lines
2.0 KiB
Plaintext
# The Python that pgAdmin builds against and ships.
|
|
#
|
|
# The Windows and macOS packaging read this file. Both ship an interpreter
|
|
# inside the package, because the one on the user's machine may be missing
|
|
# altogether or far too old, so the version has to be decided somewhere; fixing
|
|
# it here means a given commit produces the same interpreter rather than
|
|
# whichever one happened to be installed on the machine that ran the build, and
|
|
# that a change of version arrives as a reviewable commit rather than as a
|
|
# settings change somebody made on a build agent.
|
|
#
|
|
# The Linux packages do not read it and should not: they depend on the
|
|
# distribution's Python, which is the distribution's business rather than ours.
|
|
#
|
|
# The format is deliberately dull: KEY=value, one per line, with # comments. It
|
|
# has to be read by a batch file, a shell script and occasionally a person, and
|
|
# anything richer than this would need a parser in at least one of those.
|
|
#
|
|
# PYTHON_VERSION is the exact CPython release, and is the only value the macOS
|
|
# build needs, since relocatable-python fetches the framework from python.org
|
|
# by version. The Windows build fetches a relocatable distribution from
|
|
# astral-sh/python-build-standalone, whose releases are dated rather than
|
|
# versioned, hence the second value; it then ships the matching embeddable
|
|
# distribution from python.org.
|
|
#
|
|
# The two must be changed together, because the archive names embed both, as
|
|
# cpython-<PYTHON_VERSION>+<PYTHON_BUILD_STANDALONE_TAG>-<platform>.tar.gz, and
|
|
# any given tag only carries the CPython releases that were current when it was
|
|
# cut.
|
|
|
|
# This stays on 3.13 for now. The Windows build needs pywinpty, which
|
|
# requirements.txt holds at 2.0.x because of
|
|
# https://github.com/andfoy/pywinpty/issues/545 (reads from the psql process
|
|
# lag behind what is typed in 3.x), and 2.0.x has no wheel for 3.14 and cannot
|
|
# be built for it, since its PyO3 supports nothing newer than 3.13. Move to
|
|
# 3.14 once pywinpty 3.x is shown to work in the PSQL tool on Windows.
|
|
|
|
PYTHON_VERSION=3.13.16
|
|
PYTHON_BUILD_STANDALONE_TAG=20261013
|