On mar. 18 sept. 2012 11:33:30 CEST, Pierre-Yves David wrote: > On Mon, Sep 17, 2012 at 11:03:01AM +0200, afayolle wrote: >> On lun. 17 sept. 2012 10:34:44 CEST, Sylvain Thénault wrote: >>> On 17 septembre 10:20, afayolle wrote: >>>> On ven. 14 sept. 2012 14:01:01 CEST, Sylvain Thénault wrote: >>>>> * deprecate disable-all >>>> >>>> You're sure about that one? >>> >>> do you see any valid reason to keep it if we have an equivalent working >>> similarly on command line and using inline comments, while disable-all >>> only work inline? >> >> The scope and usage is a bit different, IMO : --disable=all is meant to >> remove everything everywhere and selectively enable stuff everywhere, >> while #pylint: disable-all is meant to completely skip checking a file. > > That's confusing…
What is ? If you'd rather have a different alias for --disable=all, that's easily fixed. Just tell me what is better in your opinion If you'd rather have a different directive for disable-all, that's possible too, but is potentially a PITA for end users which use this in their code and will have to deal with the deprecation warning until their teams have migrated to the new pylint version . _______________________________________________ Python-Projects mailing list Python-Projects@lists.logilab.org http://lists.logilab.org/mailman/listinfo/python-projects
