On 09 avril 11:47, Claudiu Popa wrote: > On Wed, Apr 9, 2014 at 10:25 AM, Sylvain Thénault > <sylvain.thena...@logilab.fr> wrote: > > > > * pylint pull request triage: merge the ready-and-not-controversial ones, > > provide/ask feedback for others > > > > * pylint issues triage: close the resolved, open the acknowledged new ones, > > ask > > feedback when necessary, and see if there are some show-stopper (probably > > not) > > > > Any help, notably on the two last points, is very welcome. > > -- > > 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 > > > Issue 180 seems potentially problematic, the user marked it as critical.
Yep. Being removed from popular CI tools would be bad for pylint. We can easily add support back from the -i/--include-ids, marking it as deprecated and emiting warning when used. It would be great if it could be omitted from --help and from generated config (the first one is easy using 'level', don't know for the second). Anyway, the OP should be warned that accepting and ignoring the option is the best we can do, it will much probably remains problems when attempting to parse the output (as it won't be in the expected format). -- 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
