Todd Rme píše v Po 10. 02. 2020 v 10:51 -0500:
From the previous discussion on python2 eol [1], we were given the instruction:
Specifically, do not add more skip_python2 definitions, we will do it on the project/distro level later, no need to do it for each package individually.
But what about packages that drop python2 upstream? I am getting more and more such packages, but I am unclear if I can submit updates that drop python2 support (if there are no python2 dependencies current), or whether I should hold off on updating these packages until python2 is dropped in general.
-Todd
Honestly at this point I expected us to have default skip_python2 on the singlespec, but we are still stuck on salt to vacate python3.8 staging and proceed onwards. If you wanna bump, then bump ahead honestly, we can hold it in develprj until it proceeds forward. I accepted few of those from Marketa already, I just didn't forward them to TW as I know they would break stuff until we really switch by default to off. Note that if salt is merged (and 3.8 python released) we will get the staging and focus only on the breakages there, the py2 disablements afecting the other leaf packages will most like be needed to be done by the bugowners/maintainers of the leaf pkgs. Cheers TomN�����r��y隊Z)z{.��r�'��칻 �&ޢ���� ����'��-���w�zf���^�ˬz������ ޮ�^�ˬz��