Great news, sound very cool. About the format, I really like the Clang format. I worked on a new pylint reporter and I tried several format. The message id seems to be the clearest (screenshot given in attachment).
What could be really cool is an cli option to show message numeric id or symbolic names. Examples: C:228,0: Line too long (86/80)[C0301] C:228,0: Line too long (86/80)[line-too-long] I hope it will be available for all reporters. Thanks again for the proposal and the patch. 2012/9/3 Sylvain Thénault <[email protected]>: > On 01 septembre 08:14, Martin Pool wrote: >> On 31 August 2012 18:53, Sylvain Thénault <[email protected]> >> wrote: >> >> > I would have expected the message string to rather replace the message, >> > similarly as e.g. lintian: >> >> This style, with the message and also the id, is like what clang does >> <http://clang.llvm.org/docs/UsersManual.html#diagnostics>, like >> >> RootViewController.m:50:9: warning: unused variable 'a' [-Wunused-variable] >> >> I want to eventually turn it on in a build file used by many people >> and if the messages people are used to suddenly go away it may be >> confusing, whereas if it just gets more information they can learn how >> to control that message. The symbols have to be biased more towards >> concision than comprehensibility. > > That's fine by me, I was simply expressing my opinion on the topicc :) > -- > Sylvain Thénault, LOGILAB, Paris (01.45.32.03.12) - Toulouse (09.54.03.55.76) > 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 > [email protected] > http://lists.logilab.org/mailman/listinfo/python-projects _______________________________________________ Python-Projects mailing list [email protected] http://lists.logilab.org/mailman/listinfo/python-projects
