python + sysconfig gives ANOTHER path comparing to distutils

[socketpair]

$ python3 
Python 3.11.3 (main, May 24 2023, 00:00:00) [GCC 13.1.1 20230511 (Red Hat 13.1.1-2)] on linux
Type "help", "copyright", "credits" or "license" for more information.
>>> import distutils.sysconfig
>>> print(distutils.sysconfig.get_python_lib(1,0))
/usr/lib64/python3.11/site-packages
>>> import sysconfig
>>> print(sysconfig.get_path("platlib"))
/usr/local/lib64/python3.11/site-packages

So, the changes around #769 make AGAIN

error: pythonmod: cannot initialize core module: unboundmodule.py

Is it possible not to hardcode (at ./configure stage and then in Makefile) the path at all ?

https://bugzilla.redhat.com/show_bug.cgi?id=2213996
mesonbuild/meson#10459 (comment)

[socketpair]

https://hackmd.io/@python-maint/BkqScKJW5

[socketpair]

rpm-software-management/dnf#1782

This function can be used to determine where files should be installed, but it doesn't necessarily tell you where they have been installed.

[socketpair]

And for me, I would completely drop Python 2.x support. In 2023, it is definitely dead. But that's another suggestion.