[..]
I'm only curious why to make transition to python 3.9 was chosen "debianised way"?
Originally was python package. Than was python python2 and python3. Now it is python3.9.
Why not is used still and just python and to provide necessary dependencies during transition python3.8?
That way as well is casing that with each python major version upgrade all macros needs to be multiplied.
All that was possible to avoid bu just unversioned packages names and unversioned python macros hiding major version transitions in macros.
All that is causing that for each that many packages will needs to be specially modified to produce proper results on new python version as well instead just retesting new standard macros definition on new python and/or do couple of tweaks only ion those macros definitions and nothing more).
All that it is nothing more than creating huge amount of work which needs to be done on each major version upgrade on maaaany packages.
"Making some mistakes is not the problem but repeating them again and again really is".
From that point of view with 3rd iteration should be enough to learn some lessons because now (again) looks like it will be necessary to add many modifications across many packages with python modules .. pointless!!!
Generalised build procedure with macros suppose to hide some details like versions and other.
For some reasons looks like that completely stopped in case of only python IMO because some people saw how some things has been done on Debian (successfully but with way to big overhead).
kloczek