Till now we have been using the python interpreter and entering code directly on the command line. From this point, we will use source code files and run them via the python compiler.<\/p>\n
<\/p>\n
Any program will have errors. There are two kinds of errors:<\/p>\n
<\/p>\n
Syntax errors are errors which python shows when you ask it to run some code. These errors happen because the code does not follow the rules of syntax of Python. Examples are given below:<\/p>\n
>>> \r\n>>> print 10 + \"word\"\r\nTraceback (most recent call last):\r\n File \"<stdin>\", line 1, in <module>\r\nTypeError: unsupported operand type(s) for +: 'int' and 'str'\r\n>>> print 10 \/ 0\r\nTraceback (most recent call last):\r\n File \"<stdin>\", line 1, in <module>\r\nZeroDivisionError: integer division or modulo by zero\r\n>>> c = a + * b\r\n File \"<stdin>\", line 1\r\n c = a + * b\r\n ^\r\nSyntaxError: invalid syntax\r\n>>><\/pre>\n<\/p>\n
Syntax errors are easy to spot since Python itself points it out. Your programs will not run if they have syntax errors.<\/p>\n
Runtime Exceptions are errors which occur during the execution of the code. This can happen due to various conditions. Some examples are given below:<\/p>\n
set1 = {1,2,3,4,5,6}\r\nset2 = None\r\n\r\nprint set1.intersection(set2)<\/pre>\n<\/pre>\nOutput:<\/p>\n
Traceback (most recent call last):\r\n File \"exceptions.py\", line 6, in <module>\r\n print set1.intersection(set2)\r\nTypeError: 'NoneType' object is not iterable\r\n\r\n<\/pre>\nPython provides a way of handling Exceptions in your code so that you can handle it as required and not have the program crash. When an exception is raised<\/em>\u00a0 you can handle <\/em> it using the try except<\/em> control structure. Each kind of Exception has a name and there are many Exceptions predefined in Python eg. TypeError. RangeError, NameError etc.<\/p>\n
At its basic usage a try except <\/em>can be set to handle any Exception which occurs within its statements as shown below:<\/p>\n
set1 = {1,2,3,4,5,6}\r\nset2 = None\r\n\r\ntry:\r\n print set1.intersection(set2)\r\nexcept:\r\n print \"Exception handled\"<\/pre>\nOutput:<\/p>\n
Exception handled<\/pre>\nWe executed the same code above with a try except<\/em> statement. But we can be more specific about what exception we want to handle by adding the name of the Exception to the control structure:<\/p>\n
set1 = {1,2,3,4,5,6}\r\nset2 = None\r\n\r\ntry:\r\n print set1.intersection(set2)\r\nexcept TypeError:\r\n print \"Exception handled\"<\/pre>\nOutput:<\/p>\n
Exception handled<\/pre>\nIf you put the wrong Exception name then it will not work:<\/p>\n
set1 = {1,2,3,4,5,6}\r\nset2 = None\r\n\r\ntry:\r\n print set1.intersection(set2)\r\nexcept NameError:\r\n print \"Exception handled\"<\/pre>\nOutput:<\/p>\n
Traceback (most recent call last):\r\n File \"exceptions.py\", line 7, in <module>\r\n print set1.intersection(set2)\r\nTypeError: 'NoneType' object is not iterable<\/pre>\nYou can handle multiple Exceptions within a try except <\/em>block by passing the exception names within brackets. Assigning a variable to the Exception allows you to examine the actual Exception which was handled.<\/p>\n
Note that if you are catching multiple Exceptions then only one of them will be caught – whichever one happens first. Once execution enters into the except <\/em>block then it will not go back and execute the rest of the statements within the try <\/em>section.<\/p>\n
<\/p>\n
set1 = {1,2,3,4,5,6}\r\nset2 = None\r\n\r\ntry:\r\n print 12\/0\r\n print set1.intersection(set2)\r\nexcept (TypeError, ZeroDivisionError) as err:\r\n print \"Exception handled \" \r\n print err<\/pre>\nOutput:<\/p>\n
Exception handled \r\ninteger division or modulo by zero<\/pre>\nAs you can see above, the division by zero exception was handled and then it exited the try except <\/em>block without executing the set1.intersection(set2) <\/em>statement.<\/p>\n
In the next post, we examine Directory Management<\/a>.<\/p>\n
<\/p>\n","protected":false},"excerpt":{"rendered":"