2011/2/18 Jürgen Hermann <[email protected]> > > There are already message categories, but maybe "policies" could be added > to group options and enable/disable the whole group of messages at once. > > How about this: add the concept of "profile" or "policy", which is more or > less a selectable addendum to .pylintrc, loaded before .pylintrc, let it > have the same format as that (re-use pylintrc reader code), and merge it (in > memory) with the user-specific .pylintrc. > > pylint then could distribute pre-defined profiles > (pylint/profiles/default.rc, pylint/profiles/pep8.rc, > pylint/profiles/all.rc), and in addition look at ~/.pylint/profiles for > locally defined profiles. > > You could then do things like "pylint -P pep8 mypkg", or "pylint -P > seldom_but_detailed mypkg".
Is there any real practical need for this concept at the time being though? The most difficulty I have in configuring pylint stems from tweaking accepted class name patterns and such. The real problem I have with pylint is noise (typically false positives), and breakage (more or less) from not dealing very well with Python eggs for instance. Arve
_______________________________________________ Python-Projects mailing list [email protected] http://lists.logilab.org/mailman/listinfo/python-projects
