Make Pylint usable

Pylint now shows large amount of warnings. This makes us not use it after making some changes to code, which brings even more new warnings.

The goal is to split pylintrc-lib to two separate files: pedantic and non-pedantic one, and then fix most of the errors in non-pedantic pylint, so we can start using it again... at least in non-pedantic mode with some warnings ignored.

assigned to @Jakub.Judiny

By Jakub Judiny on 2024-12-26T14:08:03

added C-Dev-Tools P4 S-New T-Task labels

changed milestone to %Backlog

Relation 'relates' to: 7654

By Jakub Judiny on 2023-05-09T15:41:26

added S-In Progress label and removed S-New label

added S-Resolved label and removed S-In Progress label

Merged into devel.

But it won't be that usable until #7654 is solved.

By Rajmund Hruška on 2023-05-29T12:36:57

added S-In Review label and removed S-Resolved label

changed milestone to %2.11

On GitLab we get a lot of C0411 warnings, e. g.

lib/hawat/blueprints/detectors/test/__init__.py:19:0: C0411: third party import "import hawat.const" should be placed before "from mentat.datatype.sqldb import DetectorModel" (wrong-import-order)

as seen in the log - https://gitlab.cesnet.cz/713/mentat/mentat/-/jobs/9847/raw.

This happens basically in every hawat file, because the imports from mentat precede those from hawat and mentat is considered a third party library. These warnings are not present on buildbot and my machine, though. I wonder why.

By Rajmund Hruška on 2023-06-20T14:06:04

Relation Relates - Bug 7654 pylint job on buildbot takes too long

By Pavel Kácha on 2023-06-23T09:38:50

From 2023-06-22 meeting:

• would be nice to add test for 3.X SQLAlchemy with big fat warning to review the necessity for the patch close to the patching part of the Makefile
• then let's move this issue (or #7654?) into deferred (with similar note - to recheck on 3.X)

By Pavel Kácha on 2023-06-23T09:41:45

changed milestone to %Future

added S-Closed label and removed S-In Review label

changed milestone to %2.12

closed