<https://lh3.googleusercontent.com/-DTQ2DsQ9qyw/V8XqmU6F2TI/AAAAAAAABZM/k_8hNL7ai48x43ljPYU1poB5Uf_P5y3QQCLcB/s1600/Report.png> That is the report from the Sonar with all the rules included. Unfortunately, I cannot export it as a PDF or some more convenient format. I can describe all the steps in my blog so some of the Django members could set up Sonar on his/her machine and see a lot more details and figure out if it's worth it to fix some of the issues.
On Sunday, August 28, 2016 at 11:16:57 PM UTC+3, Aymeric Augustin wrote: > > On 28 Aug 2016, at 21:43, Ivan Sevastoyanov <ivan.sev...@gmail.com > <javascript:>> wrote: > > > My question is do you consider using SonarQube for code quality > analysis, static analysis and find bugs because it's able to do that. > > > I guess that depends on the signal / noise ratio in the things SonarQube > flags. > > Perhaps you could do an initial run and see whether SonarQube spots > interesting bugs? > > I have no idea what the results could be because I’m not familiar with > static analysis of Python code. > > -- > Aymeric. > > -- You received this message because you are subscribed to the Google Groups "Django developers (Contributions to Django itself)" group. To unsubscribe from this group and stop receiving emails from it, send an email to django-developers+unsubscr...@googlegroups.com. To post to this group, send email to django-developers@googlegroups.com. Visit this group at https://groups.google.com/group/django-developers. To view this discussion on the web visit https://groups.google.com/d/msgid/django-developers/23796c29-182d-4e72-931b-38ba27dd2581%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
