On 17 septembre 11:03, 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.
Humm, right. I've not often used it. Then I would say this option is misnamed, and should rather be named skip-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) I would rather go to a renaming of this option, which becomes somewhat unrelated to your change. -- 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 _______________________________________________ Python-Projects mailing list Python-Projects@lists.logilab.org http://lists.logilab.org/mailman/listinfo/python-projects