Where was a semantic mistake in OP’s code is in Abhishek Arya’s answer

TL;DR – early return:

def your_function():
    if not should_do():
        return # NO RETURN VALUE!
    # rest of the function

…yes, this will no longer emit the inconsistent-return-statements 😉

This Q/A pops also when you search for inconsistent-return-statements, I want to give a brief "common problems" guide for those.

Case A: return value is irrelevant, you just want to exit function early

There are cases, where there are functions (or "procedures" if you want to get technical about it) that just do something, but are not expected to have any return values AT ALL,

at the same time, there may be e.g. some sort of check at the start of the function whether this function run even makes sense, what may first come to your mind, is wrapping the whole function code in an if statement:

def your_function(article):
    if display_content():
        content = get_content(article)
        # do some extensive logic to generate final content
        # ...
        print(content)

…this is oversimplified, but let’s hope you can imagine how such coding can pretty quickly fall into a "spaghetti code" if there are more checks and more code in general + it also steals that one "tab" of a space that you so desperately need to fit into your project’s max line length.

Luckily, same as in many other programming languages, there IS a way of an early ending of a function by returning at ANY place within the function run, meaning in any "Control Flow" – including if/elif/else, for/while loops, …

Now you’d probably jump quick to just return None, False, etc. although it would work, you’d still get the pylint inconsistent-return-statements warning – to understand why let’s see the warning’s message:

Either all return statements in a function should return an
expression, or none of them should. pylint(inconsistent-return-statements)

From pylint’s point of view, if you put anything after the return it will be considered as an expression. So what to do? Actually, in Python, you CAN return "nothing" (again this is not unique to Python)

def your_function(article):
    if not display_content():
        return

    content = get_content(article)
    # do some extensive logic to generate final content
    # ...
    print(content)

Although in Python returning "nothing" should be (and technically, to my knowledge, it is) an equivalent of return None, by physically writing "None" you are expressing the intention no matter the implicity of it.

Don’t confuse this though with pylint(assignment-from-none) (Assigning result of a function call, where the function returns None) – where both "return" AND "return None" are considered as returning None!

Case B: Your function has a case when it doesn’t return

Quite common mistake especially in a larger code is to create a code part which results in simply not returning anything. This is not exactly OP’s case, since they used just a negation of the same condition, but pylint doesn’t know that, so here’s its thought process:

if SOME_CONDITION: # ok, here's just another condition
    return someReturnExpression # and ok, it returns SOMETHING, let's note that
elif OPPOSITE_OF_SOME_CONDITION: # ok, here's just another condition
    return someReturnExpression # and ok, it returns SOMETHING, let's note that
# WAIT ! What?! THERE WAS NO "else:"! Hmmm...
# ...what happens if both conditions fail? NOTHING WOULD BE RETURNED!
# We need to make a warning about that!
# (fact that sometimes they return SOMETHING and sometimes NOTHING)

So this inconsistent-return-statements could be resolved with

if SOME_CONDITION: # ok, here's some condition
    return someReturnExpression # and ok, it returns SOMETHING, let's note that
else: # ok, here's else
    return someReturnExpression # and ok, it returns SOMETHING, let's note that
# Ok, so if returns SOMETHING, else returns SOMETHING,
# so SOMETHING is returned every time! that's good!

…this in itself works, but it will generate yet another pylint issue

Unnecessary "else" after "return" pylint(no-else-return)

See python actually encourages early returns since it often leads to a cleaner code.

return during function run ENDS(/exits) the function and pylint sees that – it sees that if the condition was true, the function code would simply end there – so what it, Abhishek Arya, me and many others suggest is simply continuing with the code after the if part:

if SOME_CONDITION:
    return someReturnExpression

# ... some more code ...
# ... some more code ...
return someReturnExpression

Case C: Combination

Simply don’t combine "just" return with return SOMETHING,

if you really need to return None, simply explicitly return None in that case

def get_article(id):
    article = find_article(id)
    if article.id == 0:
        return None

    return article

This is just an example, this is not how you’d really check for some articles 😉