New flag for avoid assert statements in CC about radon HOT 5 CLOSED

Mhmm it seems fair. How do you propose to call it? --no-asserts / --no-assert / --exclude-assert? I tend to dislike the last one because it starts like another option which is already present. Also I'm not sure if this option would need a short flag too. It does not seem very common.

from radon.

It seems two good choices. Maybe "–avoid-assert" could be an option too, but I think the first ones are best.
I was thinking in –O, but it won’t be a good idea. The –O option doesn’t mean avoiding assertion statements, but optimizing the code (although the only optimization is to avoid asserts).

from radon.

Yeah, I thought about -O as well, but I excluded it. So I'll go with --no-assert, which seems the most intuitive and obvious to me.

from radon.

I think a --no-assert option would be perfect.

As an aside, I'd like to add that with the current situation, using plain assert in the unit tests would increment the CC but using, for example, assertEqual -like methods from common unit testing frameworks would not. For me, that's another reason to provide --no-assert.

from radon.

That's because a plain assert is a statement, while assertEqual is a function. So the complexity gets hidden inside it.

from radon.