[code-quality] Change in error messages in pylint 1.1

Sylvain Thénault sylvain.thenault at logilab.fr
Fri Jan 17 07:32:12 CET 2014


On 16 janvier 10:50, Mark E. Hamilton wrote:
> Hi,

Hi Mark,
 
> When we updated to pylint 1.1 many of the messages changed. In
> particular, the invalid-name (C0103) message used to say:
> 
> ... Invalid name "Test_which" for type class (should match
> [A-Z_][a-zA-Z0-9]+$)
> 
> which was really useful, since (if you understand regular
> expressions) it tells the user exactly what the name pattern should
> be. Now, however, it only says:
> 
> ... Invalid class name "Test_which"
> 
> This is less than useful, since as a user I might not know where to
> go to find out what the RE is that was matched against. The messages
> generated by --list-msgs only shows the general message:
> 
> :invalid-name (C0103): *Invalid %s name "%s"*
>   Used when the name doesn't match the regular expression associated
> to its type
>   (constant, variable, class...).
> 
> which doesn't help.
> 
> The default REs show up in the --long-help output, but a user has to
> run that manually, then look for the option which affects the
> particular message he is seeing.
> 
> Is there a way simple way to get the REs on the generated html pages again?

I'm afraid not. You should file an issue in the bitbucket tracker:
https://bitbucket.org/logilab/pylint

Thank you for your feedback, regards,
-- 
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


More information about the code-quality mailing list