Cyclomatic Complexity

Question

Does anyone know if this is good or bad?

    F 97:0 list_of_weights_to_number - B (8)
    F 75:0 xkcd_to_list_of_weights - A (3)
    F 36:0 decode_XKCD_tuple - A (2)
    F 58:0 decode_value - A (1)

4 blocks (classes, functions, methods) analyzed.
Average complexity: A (3.5)

Answer 1

Mine is 4.25 so that's got to be good. And some things just can't be further optimised, so as long as you can't find a better way, you don't have to worry about it too much.

Comments

What's better,  a higher or a lower score?

---

the lower the better

Answer 2

Cyclomatic complexity expresses the intricacy of your code and how much better you can do.

https://en.wikipedia.org/wiki/Cyclomatic_complexity

If i remember correctly it also gives some bonus points to the final score of the HW. Not sure though.

A is a good point

B is not as good as A

Anyway the easier the better. Use fewer IFs and LOOPs and when too many just split some task to another function, then you r good to submit.

Comments

Oh, so we can "cheat" by splitting a function into smaller functions?

---

In previous years, a low cyclomatic complexity used to give a bonus. However, to encourage better code quality, from this year on the cc is checked through a test and therefore can only give a penalty for high cc.

Answer 3

We are using 10 as a limit

Answer 4

That is a solid result. A1 is the best option, and with B, C etcetera, and increasing numbers, it gets worse; so that average is quite good.

Answer 5

How did you get that ?

Comments

Run radon cc -a -s --show-closures program01.py 

---

thanks for the quick answer