{"id":37326,"date":"2016-08-31T12:55:42","date_gmt":"2016-08-31T17:55:42","guid":{"rendered":"http:\/\/luispalominotblog.wordpress.com\/?p=716"},"modified":"2016-08-31T12:55:42","modified_gmt":"2016-08-31T17:55:42","slug":"you-are-the-only-exception","status":"publish","type":"post","link":"https:\/\/kenscourses.com\/tc101fall2016\/syndicated\/you-are-the-only-exception\/","title":{"rendered":"You are the only Exception"},"content":{"rendered":"

--Originally published at Programming<\/a><\/a><\/em>
<\/p>\n

Introduction to Exceptions<\/h2>\n

It’s been a long journey for some of you. Whether you’ve spent 10+ hours coding or just a couple, I’m pretty sure you are familiar with the error messages that the console displays when your code is wrong. So far you don’t care if the user enters a number when they are supposed to enter a string, but that’s from the past. It’s now time for us to take the next step and start handling exceptions. By now you should know that there\u00a0are at least two important noticeable\u00a0kinds of errors: syntax errors and exceptions.<\/p>\n

Syntax Errors<\/h2>\n

Probably one of the most common kind of errors for the people that are still in the process of learning Python. The console will print a Syntax Error message showing you with an arrow ^ the earliest point in the line where the error was detected, followed by the number of the line so you\u00a0know where to look.
\n\"1.png\"<\/p>\n

\"2.png\"<\/p>\n

Exceptions<\/h2>\n

A statement or an expression can be syntactically correct and yet,\u00a0an error may occur when the program is executed. This is caused because of an exception, which is defined as an error occurred during the execution of a program. Exceptions come in different types, some types\u00a0for the exceptions are:<\/p>\n