2007-03-01 09:31:26 +00:00
|
|
|
Since 0.17, pylint contains a Restricted python checker (rpython).
|
|
|
|
|
It contains the following checks:
|
|
|
|
|
|
|
|
|
|
* unavailable keywords / builtins
|
|
|
|
|
* multiple inheritance
|
|
|
|
|
* mixing multiple types
|
|
|
|
|
* non homogeneous list
|
|
|
|
|
* global modification
|
|
|
|
|
* negative slice index
|
|
|
|
|
* using %r in format string
|
2008-02-07 08:48:46 +00:00
|
|
|
* warn about special methods that are not implicitly called
|
2007-03-01 09:31:26 +00:00
|
|
|
|
|
|
|
|
By default the rpython checker is deactivated. Activate it using :
|
|
|
|
|
|
|
|
|
|
pylint --rpython-mode -rn ...
|
|
|
|
|
|
|
|
|
|
(-rn is disabling statistics reports) or
|
|
|
|
|
|
|
|
|
|
pylint --enable-checker=rpython ...
|
|
|
|
|
|
2008-02-07 08:48:46 +00:00
|
|
|
to get only rpython checks (though in this case you won't be warned about
|
2007-03-01 09:31:26 +00:00
|
|
|
regular errors).
|
|
|
|
|
|
|
|
|
|
Another interesting thing is the rpython dedicated testing framework,
|
2008-02-07 08:48:46 +00:00
|
|
|
testing that checked things are actually not translatable. I have the idea
|
2007-03-01 09:31:26 +00:00
|
|
|
that this may be useful to generate some kind of documentation for
|
|
|
|
|
features supported by rpython or not, and help spread information when a
|
|
|
|
|
feature that wasn't supported is introduced in rpython. That's another
|
|
|
|
|
story though... If you're interested, check
|
|
|
|
|
pylint/test/test_rpycompilation.py.
|
