Friday, September 9, 2016 at 10:01:52 PM UTC+3, Ivan Sevastoyanov wrote:
>
> Hello,
>
> I installed some older versions of SonarQube and unfortunately the rules
> are not the same and the report generated is not full. But I reviewed the
> issues and I did not find any secu
setting up
SonarQube, sonar-scanner and Python plug-in and post it here. It takes not
more than 15 minutes, so you can see the issues yourself.
Regards,
Ivan
On Tuesday, September 6, 2016 at 3:32:41 PM UTC+3, Ivan Sevastoyanov wrote:
>
> Hello,
>
> I'm back from the vacation.
>
&
Hello,
I'm back from the vacation.
@Hanne Moa - As far as I know, you can skip packages, files and everything
can be customized. It's the same with the rules. I did not prioritized the
Sonar rules - they are the default ones and Sonar is detecting not only
possible bugs and issues but code
uestion: why use sonar instead of something like pylint/pep8 -
> these tools also provide static analysis and report common violations in
> the Python world.
>
> On Wednesday, August 31, 2016 at 7:50:38 PM UTC+2, Ivan Sevastoyanov wrote:
>>
>>
>> <https:/
major issues by groups.
Regards,
Ivan
On Wednesday, August 31, 2016 at 2:15:48 PM UTC+3, Tim Graham wrote:
>
> Any security issues should be reported to secu...@djangoproject.com
> , otherwise it's fine to share the information here.
>
> On Wednesday, August 31, 2016 at 2:25:55 AM UTC
the whole report in a convenient format.
Regards,
Ivan
On Wednesday, August 31, 2016 at 12:55:35 AM UTC+3, Tim Graham wrote:
>
> Perhaps you could tell us about some of the critical issues so we could
> get a sense for that.
>
> On Tuesday, August 30, 2016 at 4:26:42 PM UTC-4, Iv
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 Sevastoyan
wrote:
>
> On 28 Aug 2016, at 21:43, Ivan Sevastoyanov <ivan.sev...@gmail.com
> > 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 th
"code smells". That way we can prioritize some of the findings for fixing
in the next releases.
PS: I accept the criticism and won't use guys annymore :)
Regards,
Ivan
On Sunday, August 28, 2016 at 10:23:02 PM UTC+3, Aymeric Augustin wrote:
>
> On 28 Aug 2016, at 20:46, Ivan Sevast
Hi guys,
I am new to Django and I want to contribute to the project soon. Sorry for
the question if it's not appropriate. Do you consider using SonarQube (or
something similar) for code quality analysis?
Regards,
Ivan
--
You received this message because you are subscribed to the Google
10 matches
Mail list logo
