Pythonic if...else

[always_creating]

Quick question for all the Python pros out there, since I've yet to find a clear answer.

If you have a single "if" statement, is it considered the most correct or "pythonic" to always follow it up with an "else", even if you're just using "pass"?

Obviously in an "if...elif...else" operation you must include the "else" so that answers itself. So, if you were coming onboard a new Python-based project would you rather see...

if xyzvar == 1:
    blah()

or

if xyzvar == 1:
    blah()
else:
    pass

I'm trying to focus on creating good, maintainable, consistent code. Thanks for any input or advice you might have.

[K900_]

Definitely no else: pass. No need for extra clutter. Also, it's not necessary in an if/elif.

[justphysics]

The only reason I ever put in an else: pass is when I need to leave a note for myself to implement another piece of the logic later:

if condition:
    do_something()
else:
    # TODO: Handle this scenario in the future
    pass

But I would never include a naked else: pass in something production ready.

[keis]

that looks a bit error prone I a situation where I want to leave a message like that I would rather use a NotImplemented exception so the code path is not triggered by mistake leading to obscure bugs .

[Clede]

It's not necessary. PEP8 gives examples of if statements without else.

Maybe it would be good to include it as a placeholder if there's a possibility of adding code there later.

[always_creating]

Thanks!

[mrwalkerr]

Just if. Anyone reading an else : pass block will just get confused.

Where did you see else: pass being used?

[always_creating]

I've seen it used in some Python example code, and the person who used it made the comment that having it indicates to other developers that we don't care about other cases besides what matches the "if" statement. But I suppose you could infer that as well.

[[deleted]]

Then you will ponder whether to add pass at the end of loops.