On 22 août 13:16, Claudiu Popa wrote:
I'm really enjoying this idea of providing entry-points for Pylint's reports. Currently we have a way to customize the format of the reporting, either it be text, html, json or anything else that the user needs, but no way of providing a hook into pylint's analysis for generating reports such as the ones we have right now. They're currently "hardcoded" and entwined within pylint's internals. Ian, I'll appreciate your help on this one.
I'm not sure about what you want here. Reports are currently declarated by checkers, because they usually rely on data gathered using the checker API. Do you mean we should avoid checker that mix actual checks and data gathering for reports?
Most probably, after having this mechanism, the reports will be moved into a third party package, which can be activated on a need by need basis, so that no one loses the current functionality if they're using it and no one needs to install third party reports if they don't need reports at all.
I'm fine with that, though I still think the note thing should be kept activated by default, especially for new comers. This could be as simple as one extra line at the end of the analysis. -- 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