On 2023/01/11 17:04, Jan Stary wrote: > The python-3.10 port provides a 'python3' symlink, > but python-3.11 does not. This makes build systems using AM_PYTHON, > such as libsndfile's ./configure as produced by automake-1.16.5, > _miss_ python, because python.m4 does this: > > AC_DEFUN([AM_PATH_PYTHON], > [ > dnl Find a Python interpreter. Python versions prior to 2.0 are not > dnl supported. (2.0 was released on October 16, 2000). > m4_define_default([_AM_PYTHON_INTERPRETER_LIST], > [python python2 python3 dnl > python3.9 python3.8 python3.7 python3.6 python3.5 python3.4 python3.3 dnl > python3.2 python3.1 python3.0 dnl > python2.7 python2.6 python2.5 python2.4 python2.3 python2.2 python2.1 dnl > python2.0]) > > So python3.10 is found via the python3 symlink, but python3.11 is not found.
With autoconf ports, python3.10 is normally found via python.port.mk setting ac_cv_prog_PYTHON / ac_cv_path_PYTHON / PYTHON in the environment. > I don't use python as such. Is that the port adding the symlink, > or the 3.10 distribution? Can we please have the symlink for 3.11 > as well? That's probably the easiest way to accommodate such systems. No, that will break installing 3.11 on a system where 3.10 is already installed. 3.10 is the default version of Python 3; that is all that other ports need to care about. 3.11 is there partly so we can gain experience before moving the default across, and partly in case people need it for non-ports/packages software (which will usually involve installing a bunch of modules themselves via pip3.11).
