On Wed, Jun 26, 2019 at 3:06 PM José Abílio Matos <jamatos@xxxxxxxx> wrote: > > On Wednesday, 26 June 2019 13.03.44 WEST Vít Ondruch wrote: > > I agree with the "# Stop linting code in %%check and measuring coverage, > > this is upstream's business" reasoning. Shouldn't we mention that > > somewhere in guidelines? > > > > > > Vít > > The funny part is that this consideration applies to more than just python. In > this case I am thinking as an example in R packages that suffer from the same > malady. :-) Well, if the linter brings actual value (shellcheck for example does) and maintainers use that to locally patch whatever fails linting and sends the patches upstream bragging that this was First discovered in Rawhide because we have the latest release of the linter, I see no problem with that :p Cheers _______________________________________________ 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
