On 24 août 09:49, Claudiu Popa wrote:
On Mon, Aug 24, 2015 at 9:39 AM, Sylvain Thénault email@example.com wrote:
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?
The initial problem occurred when I looked into removing logilab-common as a dependency for pylint. The only dependent modules left were components used by the reports and the cohesion with logilab.common is so high, that it is a real pain to remove the dependency right now. Instead, if we'll have some hooks into the reporting checkers, then the dependency can be moved outside of the project, into third party utilities.
Ah so you mean the ureport thing? This is there only to support report in different formats (mainly text and html).
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.
The note will remain, it's especially useful for newcomers.
Glad we agree on that :)