On Tue, Sep 18, 2012 at 11:36:59AM +0200, afayolle wrote: > >> 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 ?
The fact that "disable=all" does something different that "disable-all" > 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 . I think that sylvain proposal of "skip-file" is the way to go. Issuing plain Deprecation warning seems a bad idea for the reason you listed. PendingDeprecationWarning seems our way to got here. -- Pierre-Yves David http://www.logilab.fr/
signature.asc
Description: Digital signature
_______________________________________________ Python-Projects mailing list [email protected] http://lists.logilab.org/mailman/listinfo/python-projects
