On Mon, 2021-06-28 at 14:08 -0700, Khem Raj wrote: > > On 6/28/21 12:47 PM, Alexander Kanavin wrote: > > I just generally disagree with the idea that changing a = b to a=b, or > > import a,b to import a\nimport b helps readability or reduces confusion. > > I understand that this seems change for change's sake. Consistent coding > formatting goes long way in improving quality of code and reviews too. > this also help folks who are new to project due to it being a familiar > format. > > > > > I'm reading a lot of python code all the time, and never once have been > > confused by inconsistent whitespace. > > > > Can the linter fix anything else, which has actual benefit? > > > > linters always find interesting issues all the time, however the payoff > only happens once code is clean enough to run them. otherwise looking > through tonne of issues you want to ignore is manual effort and can not > be sustained. > > Persian Prince, > > I think it would be better if we have a selftest to run linter on AB > to have this effort sustained in general.
We do have it run on the AB: https://autobuilder.yocto.io/pub/non-release/20210628-15/testresults/oe-selftest-debian/pylint.log We disabled a number of the warnings we were not interested in and haven't had the time to investigate the other more important issues it flags (as yet). Cheers, Richard
-=-=-=-=-=-=-=-=-=-=-=- Links: You receive all messages sent to this group. View/Reply Online (#153397): https://lists.openembedded.org/g/openembedded-core/message/153397 Mute This Topic: https://lists.openembedded.org/mt/83838928/21656 Group Owner: [email protected] Unsubscribe: https://lists.openembedded.org/g/openembedded-core/unsub [[email protected]] -=-=-=-=-=-=-=-=-=-=-=-
