 So in the last video I was showing you a structure and one of the things that I did not include was this idea of an error type I was just saying catch everything and that's perfectly fine, but sometimes I might want to Break down into very specific errors do different messages for different errors. There's some little blocks This is a good example. There's tons of these Error types that you might deal with you'll see as we work with files IO is important and importing if you try and import something that doesn't exist But the one that you're probably most commonly seeing when you're writing your code is this value error Where it doesn't have the right type and so that's exactly what we were seeing as well If we look at our code as is that we've been working off of right? Let me If I run this code, I type in a 10 and Instead of the zero that I've been working off of what if I type in a right? Well, I run and as the code operates right now is an error occurred because I attempted to divide with the letter a but I'm catching every error Just willy-nilly every error is getting caught in the same message and does the same thing And so maybe I don't want that to happen and so I can do a few different options now in my case I can come in and do exception. Oh, sorry Value error And now suddenly this is only when I I give it values that are Incorrect, so in this case it wouldn't be the divide by zero. It would be the One of your inputs is Not a valid number Oh So I'll run that Again, I see the 10 I do the a one of your inputs is not a valid number But what happens to suddenly the divide by zero? Ten zero. Oh no the code crashes again because I'm only handling value errors I'm not handling the zero division errors Well, this is where the exception handling can sort of act like almost like an L if structure because what I can do is I can come in and Just like with L is I can make another possible situation accept zero division error print You cannot divide by zero and so again, I take this and I run it and Ten we've already seen that a still works. It should still work, but if I type by zero Now it works it. I cannot divide by zero other code must run And so it's a way for us to sort of do a listing of multiple error types