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. I can make #pylint: disable=all work in the same way as #pylint: disable-all, and mark the latter as Pending Deprecation (see https://bitbucket.org/agurney/pylint/changeset/9c4b79d793f5186da14ae6db7d00244fc27c84c5) -- Alexandre _______________________________________________ Python-Projects mailing list [email protected] http://lists.logilab.org/mailman/listinfo/python-projects
