Thank you for reporting this false negative. After having a look, it seems that the rule behaves a bit too conservatively in some cases, which also affects the non-compliant code example.
I created SONARPY-1579 to fix this.
Thanks for taking the time to look at this. Could you inform me what steps we will need to take on our end once the fix has been approved, if any?
When it’s fixed, you’ll need to upgrade to the next version of SonarQube that’s released. The ticket is currently in progress, so that means adopting SonarQube 10.4 when it comes out.
That was what I needed to know, thank you! I’ll be keeping an eye out for the release