[code-quality] Unsure how to change tests when adding new checker

[Sylvain Thénault]

Hi Skip,

On 21 juin 20:44, Skip Montanaro wrote:
> I'm working on a new class checker which complains about attributes
> which are defined but not used within the class.  This check triggers
> all sorts of warnings throughout the test suite.  What do I do?  Lots
> of expected output will have to be changed.

ths simplest is probably to add this message name to the 'pylint:disable'
pragma on top of files where it's unexpectedly triggered.
-- 
Sylvain Thénault, LOGILAB, Paris (01.45.32.03.12) - Toulouse (05.62.17.16.42)
Formations Python, Debian, Méth. Agiles: http://www.logilab.fr/formations
Développement logiciel sur mesure:       http://www.logilab.fr/services
CubicWeb, the semantic web framework:    http://www.cubicweb.org