yego.me
💡 Stop wasting time. Read Youtube instead of watch. Download Chrome Extension

if-elif-else | Intro to CS - Python | Khan Academy


4m read
·Nov 10, 2024

We can use an if statement to control that a particular block of code only executes when the condition evaluates to true. But what if we want to do something else only when the condition evaluates to false? Well, we can add another if statement and try and construct a condition that's the exact opposite of the original condition. That's a bit annoying, and sometimes the opposite condition isn't obvious, or it's super long.

To save us the trouble, Python instead lets us use an else branch. We can stick an else branch onto the end of any if statement, and any instructions indented inside the else branch only execute if the corresponding if statement's condition evaluates to false. That makes the if branch and the else branch mutually exclusive. Based on the answer to the condition, the computer decides which of the two paths to take.

The Python syntax for an else branch is just the keyword else followed by a colon. Again, we use indentation to tell the computer which lines of code are inside the else branch. An else branch must always follow an if branch; otherwise, what are we taking the opposite of?

Let's trace that execution path. If the condition evaluates to true, as normal, the computer goes on to execute any instructions indented inside that if branch. When it's done, execution jumps to the next line of code that's indented outside of the conditional. If the condition evaluates to false, the computer skips the rest of the if branch and jumps to the else branch. Then it executes any lines of code that are indented inside the else branch. When it's done, it just continues execution with the next line of code indented outside of the conditional.

Note that this execution path with an else branch is different from this, where we just have that instruction indented outside of the if statement. Here, if the condition evaluates to true, we print "mobile layout." Then we jump outside of the conditional and print "desktop layout." If the condition evaluates to false, we skip the if branch, jump outside of the conditional, and print "desktop layout." Because the instruction is not indented, it's independent of the conditional; it always executes.

However, if we indent this instruction inside an else branch instead, we only print "desktop layout" if the condition evaluates to false. If the condition evaluates to true, we print "mobile layout" and skip the else branch.

What if we have more than two cases, like a mobile, tablet, and a desktop layout? We could try to construct three mutually exclusive conditions, or we can take advantage of a shortcut and use the elif branch. The elif, or else if branch, allows us to chain multiple conditions together, starting with the if branch. The computer evaluates each condition in order until it finds one that evaluates to true. Then it chooses that branch to execute.

Note that order matters here because the computer will stop checking other branches as soon as it finds one that evaluates to true. If instead, I put this condition first, the if branch would capture any screen widths that are smaller than 760. That means that if I have a mobile screen that, say, 300 pixels, it will get captured by this first case and print "tablet layout." The computer only ever chooses one branch; it doesn't print "mobile layout," even though that condition would have evaluated to true.

We can attach as many elif branches as we want to any if branch, and then we can optionally add an else branch at the end. So we can see what the computer's doing. Let's trace each possible execution path. If the first condition evaluates to true, then the computer chooses that branch and executes any instructions indented inside of it. Then it jumps to the next line of code outside of the conditional.

If the first condition evaluates to false, then the computer goes on to check the next condition. If the second condition evaluates to true, then the computer chooses this branch and executes any instructions indented inside of it. Then it jumps to the next line of code outside of the conditional.

If the computer checks the first condition and finds that it evaluates to false, then checks the second condition, and also finds that it evaluates to false, then it moves on to the else branch. Else branches don’t have a condition, so if the computer reaches it, it just runs. So we execute the instructions indented inside the else branch, and then we jump to the next line of code outside of the conditional.

So if you have multiple related conditions in your program, it's generally better to use a chained conditional with elif and else branches instead of several independent single-branch conditionals. Chained conditionals make programs easier to read because it makes the relationship between conditions obvious. It reduces bugs because we, as the programmer, don't have to worry about making sure all our conditions are mutually exclusive and cover all possible cases.

It saves the computer some work. With independent conditions, the computer doesn't know they're related, so it'll evaluate every single one, even if it's impossible for multiple of them to be true. With chained conditionals, we give the computer the hint that these are all mutually exclusive, so it knows it can stop evaluating as soon as it finds a branch that evaluates to true.

More Articles

View All
The Disappearance of Flight 19 | Atlas of Cursed Places
This is actually the lead ship of Flight 19. Wow! The exact same plane as this is Flight 19. Yes. The final word to the men on Flight 19 have been studied and pored over. Every sentence and word analyzed, in depth, by the Navy’s after action report. And t…
Safari Live - Day 162 | National Geographic
This program features live coverage of an African safari and may include animal kills and carcasses. Viewer discretion is advised. One minute, please. Always remember to switch the lights off. We’re ready for safari! Sorry, everybody, you know sometimes t…
15 Signs You’re in Money Trouble
If you know what to look for, you can spot the signs that you’re in money trouble way before it all comes crashing down. Because your behavior shows the signs earlier than your bank account does. It seems to happen so suddenly. One month you’re fine, keep…
TRACTOR PULLS: It's Not What You Think - Smarter Every Day 276
This is an absolutely preposterous tractor and it’s pulling [Music]. Something; all these people are in these stands to watch what’s called a tractor pull because it’s awesome. The winner is whoever pulls this sled the farthest before getting bogged down …
See Through Suppressor in Super Slow Motion (110,000 fps) - Smarter Every Day 177
I have been wanting to make this video for years. A see-through suppressor with a high speed camera—COME ON! This is awesome! The problem is I didn’t have access to licenses or the equipment necessary to make it. All that changed when I met Steve. Hey, i…
Office Hours at Startup School 2013 with Paul Graham and Sam Altman
We have to sit up straight. We have lower, since this is not right. Admiral Rickover would not stand for this. Um, okay. Uh, George, Nick, what are you working on? So we are building a multiplayer programming game for teaching people how to code. So lik…