For example, ezjail: there it looks like that there "flavors" actually mean a tailored standard configuration templates that can be copied from (instead from the default base).
And when I read about the lots of work the various Python releases do cause to you, and creating "flavors" of packages, I am not sure whether it is correct to think of "flavors" as templates or, say, build lists.
For each Python program different templates what to install, depending on which Python version is installed.
If I understand correctly, these were/are different packages, which will become "flavors" so that the user can easily search for and install the "examplepythonpkg" application he wants.
Instead of having a headache finding out what of "examplepythonpkg_py_1_5", "examplepythonpkg_py_3_8", "examplepythonpkg_py_9_3" etc is the correct package to install.
But, if my assumption is correct, wouldn't then "flavors" just mean different predefined install templates, i.e. dependency package lists, for "examplepythonpkg", which are being selected automatically by the package manager, depending which Pythin is available?
Hope this makes a bit clearer what confuses me.