Looking at https://docs.python.org/3/library/importlib.html, it seems
to me you would get that error if the Python binary found by
configure.ac would be python2 and not python3. I see the list of
python version tried at line 1156 of configure.ac does not try
python3.10 or later. It should probably be extended.
FYI, I have yet to see a Python install since Python 3 was invented
which did not have a 'python2' or 'python3' program, if that version of
Python is installed. So merely using 'python3' should be sufficient
unless the OS-provided package omits it. I see that 'python3' is in the
list.
It is impossible for any given libtiff release to anticipate future
python versions, although they are likely to work. It seems important
for any given libtiff release package to continue to work for
several/many years. The build should not fail just because a new Python
release appeared.
What version does 'python3 --version' report? If it reports 3.11, then
this issue is likely the problem:
https://discuss.python.org/t/python3-11-importlib-no-longer-exposes-util/25641
Furthermore, I see mention that this facility is already scheduled to be
removed. So the current Python release will not work.
Bob
--
Bob Friesenhahn
[email protected], http://www.simplesystems.org/users/bfriesen/
GraphicsMagick Maintainer, http://www.GraphicsMagick.org/
Public Key, http://www.simplesystems.org/users/bfriesen/public-key.txt
_______________________________________________
Tiff mailing list
[email protected]
https://lists.osgeo.org/mailman/listinfo/tiff
