Hi Miro, No, I did not wanted to tell that the python 3.8 transition was badly executed. The problem was more about timing. I was fighting with Fedora 31 and we had Rawhide as replacement for F31 tests because the environment is usually not that different. However, when the switch to python 3.8 happened, there were no compose ready for Fedora 31. In the end we were with broken tests and even broken backup tests solution. I had to found third solution. On Tue, 2019-09-17 at 16:27 +0200, Miro Hrončok wrote: > On 17. 09. 19 15:58, jkonecny@xxxxxxxxxx wrote: > > To make things even worse there was a switch to python 3.8 on > > Rawhide > > which wasn't really prepared (pylint did not worked). > > I trust that your intentions were only the best when you wrote your > e-mail, but > this statement kinda surprises me. The switch to Python 3.8 was very > well > prepared and I consider it one of the smoothest switches to a new > Python version > I can remember. > Pylint is never prepared for the switch. If something crucial is > depending on > pylint, it should stop. However, when you opened this discussion. Why we are not waiting for pylint to be ready? Is there a reason? I mean pylint is one of the main linters available for python, so having python without working pylint looks kind of fragile to me. I also want to tell you thanks a lot for doing all the work about python migration it's not an easy task and you are doing great work there! Jirka _______________________________________________ devel mailing list -- devel@xxxxxxxxxxxxxxxxxxxxxxx To unsubscribe send an email to devel-leave@xxxxxxxxxxxxxxxxxxxxxxx Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/ List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/devel@xxxxxxxxxxxxxxxxxxxxxxx
