At the moment, there are lots of messages from Pylint. I usually only read them attentively when I'm about to release a new version.
Go over all the warnings and either
pylint: disable=message-name
)The goal is to quickly see whether the Pylint check succeeded or not. In this case it's also possible to make it a check that's required to succeed before a release can be made.
With the current Pylint configuration messages are manageable now. The situation isn't perfect but probably good enough to close this ticket.