It should test for "python" first, and then execute python -V to get the version and test for "version > 3". If either fails, it should test for "python3" and accept any version. If that fails it should report that it requires a "python version > 3".
The Python PEP requires the versioned `python3` command to be installed even if `python` is also installed, so I don't see the point of such complications, especially trying to do it in autoconf m4. If we require python3 say so and test for it.
geany_gtk_doc_header.m4 is entirely @b4n https://github.com/b4n ping
Does this mean it is OK? I.e. in geany's control.
Its in this Geany repo, so yeah.
Ditto gen_api_gtkdoc.py, what debian does to it is their concern.
Unless we make a pure windows build using the Microsoft tool chain, we should not look for "py".
@eht16 which Python does the new windows build use, one in msys2 that is called `python3` or a Windows install that still needs `py`? Can we drop the `py`?