https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=285957
--- Comment #60 from Tatsuki Makino <[email protected]> --- (In reply to Tatsuki Makino from comment #55) I will make a small note here :) If we take the initiative to use 3.12 and adjust it in advance, the migration should be easy :) However, the following command will fail. ktrace -f /tmp/ktrace.out -di -t cn make -C /usr/ports/devel/py-dbus/ configure FLAVOR=py312 BUILD_ALL_PYTHON_FLAVORS=1 DEFAULT_VERSIONS=python=3.11 Dependencies are provided for 3.12, but 3.11 is used during the build. This cannot be avoided by just using BINARY_ALIAS. The reason is that meson is being launched by python3.11. The find_program('python3') in ${WRKSRC}/subprojects/dbus-gmain/tests/meson.build of devel/py-dbus is treated specially by /usr/local/lib/python3.11/site-packages/mesonbuild/interpreter/interpreter.py. It seems that the value of sys.executable is assigned to a variable in /usr/local/lib/python3.11/site-packages/mesonbuild/utils/universal.py, and the value of that variable is returned. To avoid this, meson needs to be run with the same version of python flavor, and for that, meson must also support the flavor. Therefore, under the current situation, maintainers of ports that include USES=python are forced to create an environment where the next version of Python is set as the default. It is surprisingly troublesome because it includes llvm :) -- You are receiving this mail because: You are the assignee for the bug.
