Re: [openstack-dev] [all] cyclomatic complexity check in flake8 & Python 3

2017-12-18 Thread Zane Bitter
On 12/12/17 08:40, Sean Dague wrote: On 12/12/2017 08:08 AM, Thierry Carrez wrote: Zane Bitter wrote: Here's how the allegedly most complex function in Heat[5] shakes out, for example:   mccabe  py27  py36   0.2.1    14 6   0.3.1    23    23   0.6.1    23    23 I don't have a

Re: [openstack-dev] [all] cyclomatic complexity check in flake8 & Python 3

2017-12-12 Thread Thomas Herve
On Tue, Dec 12, 2017 at 2:08 PM, Thierry Carrez wrote: > Zane Bitter wrote: >> We have around 60 repos using the 'mccabe' package to do cyclomatic >> complexity checks in flake8 in their gate jobs.[1] Based on advice >> received at the time[2], the version of mccabe that we

Re: [openstack-dev] [all] cyclomatic complexity check in flake8 & Python 3

2017-12-12 Thread Sean Dague
On 12/12/2017 08:08 AM, Thierry Carrez wrote: > Zane Bitter wrote: >> Here's how the allegedly most complex function in Heat[5] shakes out, >> for example: >> >>   mccabe  py27  py36 >>   0.2.1    14 6 >>   0.3.1    23    23 >>   0.6.1    23    23 >> >> I don't have a solution to suggest, but

Re: [openstack-dev] [all] cyclomatic complexity check in flake8 & Python 3

2017-12-12 Thread Thierry Carrez
Zane Bitter wrote: > We have around 60 repos using the 'mccabe' package to do cyclomatic > complexity checks in flake8 in their gate jobs.[1] Based on advice > received at the time[2], the version of mccabe that we use in the gate > is effectively pinned to 0.2.1 by hacking (the project, not...

[openstack-dev] [all] cyclomatic complexity check in flake8 & Python 3

2017-12-11 Thread Zane Bitter
We have around 60 repos using the 'mccabe' package to do cyclomatic complexity checks in flake8 in their gate jobs.[1] Based on advice received at the time[2], the version of mccabe that we use in the gate is effectively pinned to 0.2.1 by hacking (the project, not... never mind).[3] This is